1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
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.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
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.