ECS: Random container failed to start - no log

0

Hello,

We encountered troubles with ECS on Docker on EC2. Some tasks stay a long time in provisionning state while an EC2 is available and others tasks with the same docker image and parameters succeed to start. Then, the status goes from PROVISIONNING to STOPPED with reason : "Task failed to start".

I have no logs, or info on the containers in ECS console and Cloudwatch, and did not find any tips in the EC2 logs...

Any idea on why we have this behaviour ? or a way to have more traces to investigate ?

Thanks

Valentin

  • Can you run aws ecs describe-tasks --tasks <task-id> --cluster <cluster-name> and see what it reports as the stopped reason? Task status will remain available for about an hour after the task stops.

已提問 2 年前檢視次數 241 次
沒有答案

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南