blocks|key|1691326|text|结果证明，ECS代理只能用1.7版本来提取图像，而这正是我掉下来的地方。更新代理解决了我的问题，希望它能帮助其他人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691327|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

So it turns out, the ECS agent was only able to pull images with version 1.7, and that's where mine was falling. Updating the agent resolves my issue, and hopefully it helps someone else.

blocks|key|1691319|text|这很可能是IAM角色的一个问题，如果您使用以前为ElasticBean秸秆创建的角色。确保弹性豆柄所使用的角色附加了AmazonEC2ContainerRegistryReadOnly管理策略|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1691320|来源：policies.html|1691321|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/AmazonECR/latest/userguide/ECR_IAM_policies.html^0|1M|Y|0|3|D|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

This is most likely an issue with IAM roles if you are using a role that was previously created for Elastic Beanstalk. Ensure that the role that Elastic Beanstalk is running with has the AmazonEC2ContainerRegistryReadOnly managed policy attached

Source: <a href="http://docs.aws.amazon.com/AmazonECR/latest/userguide/ECR_IAM_policies.html" rel="nofollow">http://docs.aws.amazon.com/AmazonECR/latest/userguide/ECR_IAM_policies.html</a>

blocks|key|1691373|text|ECS代理的版本1.7.0中添加了对ECR的支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1691374|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/aws/amazon-ecs-agent/blob/v1.7.0/CHANGELOG.md#170^0|6|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Support for ECR was added in <a href="https://github.com/aws/amazon-ecs-agent/blob/v1.7.0/CHANGELOG.md#170" rel="nofollow">version 1.7.0</a> of the ECS Agent.

blocks|key|2849168|text|当使用Elasticbean秸秆和ECR时，您不需要进行身份验证。只需确保用户有策略AmazonEC2ContainerRegistryReadOnly|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2849169|您可以使用(Amazon+)将自定义的EC2映像存储在AWS中。当您将Docker映像存储在Amazon中时，ElasticBean秸秆会使用环境的实例配置文件自动对Amazon注册表进行身份验证，因此不需要生成身份验证文件并将其上载到(+S3)。
但是，您确实需要向您的实例提供访问Amazon存储库中的图像的权限，方法是向您的环境的实例配置文件添加权限。可以将AmazonEC2ContainerRegistryReadOnly托管策略附加到实例配置文件以提供对帐户中所有Amazon存储库的只读访问，也可以通过使用以下模板创建自定义策略授予对单个存储库的访问权限：|blockquote|2849170|来源：docker.container.console.html|2849171|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.container.console.html^0|16|Y|0|0|3|T|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$]]|$1|I|3|J|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|K|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

When using Elasticbeanstalk and ECR you don't need to authenticate. Just make sure the user has the policy <code>AmazonEC2ContainerRegistryReadOnly</code>

<blockquote>
 You can store your custom Docker images in AWS with Amazon EC2 Container Registry (Amazon ECR). When you store your Docker images in
 Amazon ECR, Elastic Beanstalk automatically authenticates to the
 Amazon ECR registry with your environment's instance profile, so you
 don't need to generate an authentication file and upload it to Amazon
 Simple Storage Service (Amazon S3).
 
 You do, however, need to provide your instances with permission to
 access the images in your Amazon ECR repository by adding permissions
 to your environment's instance profile. You can attach the
 AmazonEC2ContainerRegistryReadOnly managed policy to the instance
 profile to provide read-only access to all Amazon ECR repositories in
 your account, or grant access to single repository by using the
 following template to create a custom policy:
</blockquote>

Source: <a href="http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.container.console.html" rel="nofollow">http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker.container.console.html</a>

We are switching from Docker Hub to ECR and I'm curious how to structure the Dockerrun.aws.json file to use this image. I attempted to modify the name as <code>&lt;my_ECR_URL&gt;/&lt;repo_name&gt;:&lt;image_tag&gt;</code> but this is not successful. I also saw the details of private registries using an authentication file on S3 but this doesn't seem like the correct route when <code>aws ecr get-login</code> is the recommended way to authenticate with ECR. 

Can anyone point me to how I can use an ECR image in a Beanstalk Dockerrun.aws.json file?

If I look at the ECS Task Definition,there's a required attribute called <code>com.amazonaws.ecs.capability.ecr-auth</code>, but I'm not setting that anywhere in my <code>Dockerrun.aws.json</code> file and I'm not sure what needs to be there. Perhaps it is an S3 bucket? Something is needed as every time I try to run the Elastic Beanstalk created tasks from ECS, I get:

<pre><code>Run tasks failed
Reasons : ATTRIBUTE
</code></pre>

Any insights are greatly appreciated.

Update I see from some other <a href="https://forums.aws.amazon.com/thread.jspa?messageID=680534" rel="nofollow">threads</a> that this used to occur with earlier versions of the ECS agent but I am currently running <code>Agent version 1.6.0</code> and <code>Docker version 1.7.1</code>, which I believe are the recommended versions. Is this possibly an issue with the Docker version?

Dockerrun.aws.json structure for ECR Repo

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们从Docker切换到ECR，我很好奇如何构造Dockerrun.aws.json文件来使用这个映像。我试图将名称修改为<my_ECR_URL>/<repo_name>:<image_tag>，但这并不成功。我还看到了在S3上使用身份验证文件的私有注册中心的详细信息，但当aws ecr get-login被推荐使用ECR身份验证时，这似乎不是正确的路径。有人能告诉我如何在豆茎Dockerrun.

问ECR回购的Dockerrun.aws.json结构
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ECR回购的Dockerrun.aws.json结构EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ECR回购的Dockerrun.aws.json结构
EN