ECS任务未启动-已停止(CannotPullContainerError:“在等待连接时取消了来自守护程序请求的错误响应" [英] ECS task not starting - STOPPED (CannotPullContainerError: “Error response from daemon request canceled while waiting for connection”

问题描述

我正在使用Fargate在ECS中启动任务，并且在挂起一小段时间后，它在STOPPED中出现了以下错误:

I'm starting a task in ECS using Fargate and after being in PENDING for a little bit it ends up in STOPPED with the following error:

STOPPED (CannotPullContainerError: "Error response from daem

展开详细信息后，我会看到

When I expand out the details I see

STOPPED (CannotPullContainerError: "Error response from daemon: Get https://id.dkr.ecr.ap-southeast-2.amazonaws.com/v2/: net/http: request canceled while waiting for connection"

有原因

(Client.Timeout exceeded while awaiting headers)

因此该任务由于某种原因无法访问该容器，但是我不确定缺少什么权限以及缺少什么资源.我已经阅读了一些，我发现的唯一真正的建议是将AssignPublicIp:ENABLED添加到AwsvpcConfiguration，但这没有帮助.

So the task can't access the container for some reason, but I'm not sure what permission is missing and from what resource. I've read around a bit and the only real suggestion I've found is to add AssignPublicIp: ENABLED to the AwsvpcConfiguration but that didn't help.

推荐答案

因此，看起来错误消息在某些时候已更改: https://aws.amazon.com/premiumsupport/knowledge-center/ecs-pull-container-api-error-ecr/有一些步骤可以解决，但提到错误 CannotPullContainerError:API错误，它可能与 CannotPullContainerError:"daem的错误响应相同?

So it looks the error message has changed at some point: https://aws.amazon.com/premiumsupport/knowledge-center/ecs-pull-container-api-error-ecr/ has steps to work through but mentions the error CannotPullContainerError: API error which might be synonymous with CannotPullContainerError: "Error response from daem?

至少对我来说，创建一个AWS :: EC2 :: VPCEndpoint似乎使我更进一步.

For me at least, creating an AWS::EC2::VPCEndpoint seems to have got me further.

这篇关于ECS任务未启动-已停止(CannotPullContainerError:“在等待连接时取消了来自守护程序请求的错误响应"的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！