blocks|key|5070211|text|请转至Clusters+>+Tasks+>+Details+>+Containers|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5070212|您可以在图“错误消息”中的红色矩形周围看到一些错误消息。|5070213|任务详情：|5070214|​|5070215|📷|atomic|5070216|5070217|错误消息：|5070218|5070219|5070220|5070221|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/82d0c2fc482ce60fd02ca6ab1eda4609.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/4749942deef531f1aaad58aa37206742.png^0|3|8|E|5|M|7|W|A|0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1F|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1G|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|O|3|K|5|6|7|1L|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1M|8|@]|D|@]|E|$]]|$1|R|3|K|5|6|7|1N|8|@]|D|@]|E|$]]|$1|S|3|M|5|N|7|1O|8|@]|D|@$9|1P|A|1Q|1|1R]]|E|$]]|$1|T|3|K|5|6|7|1S|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1T|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11|12|-4]]|13|$5|X|Y|Z|E|$10|14|12|-4]]]]

Please go Clusters > Tasks > Details > Containers

You could see some error message around the red rectangle in the figure "error message."

Task detail:

<img src="https://i.stack.imgur.com/MhDph.png" alt="task detail">

Error message:

<img src="https://i.stack.imgur.com/hp6vW.png" alt="error message">

blocks|key|2956149|text|我可能会迟到，但你可以查看容器的日志，而不是tasks。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2956150|转到失败的任务->+Details+->+Container+(底部)并打开它。就在details下面，你会看到一个Status+reason。|CODE|2956151|打开容器详情|2956152|📷|atomic|2956153|​|2956154|获取失败的原因|2956155|2956156|2956157|注意:如果您的任务运行多个容器，请根据上面的截图检查每个容器的状态原因，因为它们之间可能会有所不同。|2956158|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9b0d54bb0361be699e744b9a714fc74e.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/ed994a5a4cf667d80962ef07d979f863.png^0|D|3|0|1M|D|0|0|0|1|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1C|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|N|3|O|5|6|7|1H|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1I|8|@]|D|@]|E|$]]|$1|R|3|L|5|M|7|1J|8|@]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|S|3|O|5|6|7|1N|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1O|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12|13|-4]]|14|$5|Y|Z|10|E|$11|15|13|-4]]]]

I may be late to the party, but you can check the container logs instead of the tasks'.
Go to the failed task -&gt; Details -&gt; Container (at the bottom) and open it. Right under details you'll see a <code>Status reason</code>.
Opening the container details
<a href="https://i.stack.imgur.com/y35Gz.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/y35Gz.png" alt="Opening the container" /></a>
Getting the reason for failure<a href="https://i.stack.imgur.com/vaIaQ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/vaIaQ.png" alt="enter image description here" /></a>
Note: if your task runs more than one container, check the 'Status reason' of each container as per the screenshot above, as it can be different between them.

blocks|key|5070301|text|正如Abhinav所说，消息的描述性不强(并且使用CLI+aws+ecs+describe-tasks不会添加更多内容)。唯一的可能性是登录到主机EC2实例并读取那里的日志，或者将这些日志发送到CloudWatch+https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_cloudwatch_logs.html#cwlogs_user_data|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5070302|最可能的原因(在ECS中)是集群没有足够的资源来启动新任务。您有时可以从指标选项卡中找出原因，或者从2019年年中开始(我猜取决于您所在的地区)，您可以从CloudWatch帐户设置中启用“CPU容器洞察”，以获取有关内存和CPU预留的更多详细信息。|5070303|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_cloudwatch_logs.html#cwlogs_user_data^0|T|M|30|2V|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

As Abhinav says, the message isn't very descriptive (and using the CLI <code>aws ecs describe-tasks</code> doesn't add anything more). The only possibility is to log into the host EC2 instance and read the logs there, or send those logs to CloudWatch <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_cloudwatch_logs.html#cwlogs_user_data" rel="nofollow noreferrer">https://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_cloudwatch_logs.html#cwlogs_user_data</a>

The mostly likely cause (in ECS) is that the cluster doesn't have enough resources to launch the new task. You can sometimes work out the cause from the Metrics tab, or since mid-2019 (depending on your region I guess) you can enable "CloudWatch Container Insights" from ECS Account Settings to get more detailed information about memory and CPU reservations.

blocks|key|188420|text|您可以在服务仪表板的“事件”选项卡下获取有关任务失败的一些信息。尽管那里的信息不是很有描述性，但它们可以为您提供一个模糊的概念，确切地说是哪里出了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|188421|​|188422|📷|atomic|offset|length|188423|188424|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/3007d9fee3a55cbc71dc509eec286ba2.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

You can get some information regarding the task failure under the 'Events' tab of your service's dashboard. Though the message there aren't very descriptive, they can provide you a vague idea where exactly things are getting wrong.

<a href="https://i.stack.imgur.com/rMKn4.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rMKn4.png" alt="enter image description here"></a>

blocks|key|2956188|text|这些方法对我都不起作用。起作用的是只将其中一个服务作为基本服务(只有你确定会工作的服务)，然后查看Cloudwatch日志，最终甚至是EC2实例中的ECS日志。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2956189|#+ecs-params.yml

version:+1
task_definition:
++services:
++++myservice1:
+++++++essential:+true
++++myservice2:
+++++++essential:+false
++++myservice3:
+++++++essential:+false
++++myservice4:
+++++++essential:+false
++++myservice5:
+++++++essential:+false|code-block|syntax|javascript|2956190|ECS的黑匣子毕竟不是很友好。|2956191|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

None of those methods worked for me.
What worked was making just one of the services as essential (only the one you are sure is going to work), and then looking at Cloudwatch logs, and eventually even the ECS logs within the EC2 instance.
<pre><code># ecs-params.yml

version: 1
task_definition:
 services:
 myservice1:
 essential: true
 myservice2:
 essential: false
 myservice3:
 essential: false
 myservice4:
 essential: false
 myservice5:
 essential: false
</code></pre>
ECS's black box is not very friendly after all.

blocks|key|2100195|text|转至ECS+->群集->服务(选择您的服务名称)+->+Events|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2100196|然后单击其中一个启动失败的任务(事件列表中的长UUID+)：如下所示：|2100197|​|2100198|📷|atomic|offset|length|2100199|2100200|确保选择一个已经失败的任务，以便您可以了解它失败的原因--不要选择ECS服务仍在尝试启动的任务之一，因此尚未失败(请记住，ECS将继续尝试启动任务，直到超时时间结束)。因此，失败的任务将类似于下面的屏幕截图，您应该会看到为什么它无法启动。例如，在我的示例中，此任务无法启动，因为它没有适当的IAM角色：|2100201|2100202|2100203|2100204|有了这些详细信息，您就可以进行修复了(在我的示例中，我只需要更新我的ECS+Task角色，以包括一堆secretsmanager访问和kms:Decrypt)。|2100205|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/42c65d7467703c5748601cfc40a3e4bd.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/96844e7b04f3552e8d61c8f55b71fa58.png^0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@$I|17|J|18|1|19]]|A|$]]|$1|K|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|G|5|H|7|1D|8|@]|9|@$I|1E|J|1F|1|1G]]|A|$]]|$1|P|3|E|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]|11|$5|V|W|X|A|$Y|12|10|-4]]]]

Go to ECS -&gt; Cluster -&gt; Service (select your service name) -&gt; Events
Then click on one of the tasks that failed to start (the long UUID in the list of events): like this:
<a href="https://i.stack.imgur.com/5CANt.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/5CANt.png" alt="enter image description here" /></a>
Make sure to select a task that already failed so that you can see why it failed -- don't select one of the tasks that the ECS Service is still trying to start, and thus hasn't failed yet (remember that ECS will keep trying to start tasks up until the timeout period is over). So, a failed task will look like the following screenshot, and you should see why it failed to start. In my case, for example, this task failed to start because it doesn't have the proper IAM roles:
<a href="https://i.stack.imgur.com/QpJHh.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/QpJHh.png" alt="enter image description here" /></a>
With those details, you can make the fix (in my case, I just needed to update my ECS Task role to include a bunch of secretsmanager access and kms:Decrypt).

I'm trying to launch/run a Dockerfile on AWS using their ECS service. I can run my docker image locally just fine, but it's failing on the Fargate launch type. I've uploaded my Docker image to ECR, and I've created a cluster/service/task from it.

However, my cluster's task status simply reads "DEPROVISIONING (Task failed to start)", but it provides no logs or details of the output of my running image, so I have no idea what's wrong. How do I find more information and diagnose why ECS isn't able to run my image?

How to diagnose ECS Fargate task failing to start?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯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编辑器全新改版上线，欢迎大家体验!

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

社区新版编辑器体验调研

我正在尝试使用他们的ECS服务在AWS上启动/运行Dockerfile。我可以在本地运行我的docker镜像，但在Fargate启动类型上运行失败。我已经将我的Docker镜像上传到ECR，并且我已经从它创建了一个集群/服务/任务。然而，我的集群的任务状态简单地显示为"DEPROVISIONING (Task failed to start)"，但是它没有提供我正在运行的映像的输出的日志或详细信息

问如何诊断ECS Fargate任务启动失败？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断ECS Fargate任务启动失败？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断ECS Fargate任务启动失败？
EN