ECS/EC2 instances don't download ECR image from task definition

I uploaded my app image to a private repo on ECR, when I start my EC2 instances (autoscale group for ECS service) they hang and eventually fail with "Task failed to start". I have connected to the instances using ssh, and from what I can tell docker never tries to download the image from ECR. I have confirmed that the task definition has the ECR image url defined in the container definitions -> image field, and that the image listed there exists using docker manifest inspect. Anyone have any idea why this could be happening?

主題

容器運算

標籤

Amazon Elastic Container Registry(ECR)Amazon Elastic Container Service Amazon EC2 自動擴展容器

語言

English

json

已提問 1 年前檢視次數 564 次

1 個回答

最新
最多得票
最多評論

這些答案是否有幫助？支持正確答案，以幫助社區從您的知識中受益。

The task could fail owing to a variety of reasons. If you go under ECS --> Cluster --> service --> Events, you should see why that task failed.

專家

PiyushMattoo

已回答 1 年前

json
1 年前
There are no events for the failures. The only events shown there are 'service ... has started 1 task'. When I view aws ecs describe-tasks --tasks [task_id] the stopped reason is as follows:
"stopCode": "TaskFailedToStart", "stoppedAt": "2022-12-20T07:44:46.292000-08:00", "stoppedReason": "Task failed to start", "stoppingAt": "2022-12-20T07:44:46.292000-08:00",

There is no evidence that the ecs-agent is even downloading the repo in the first place, but the image is defined in the task definition, and docker manifest inspect verifies that the image exists. It seems like the ecs-agent is just not even starting to process the container logic for the task definition.

ECS/EC2 instances don't download ECR image from task definition

相關內容