-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ECS: Task fails to start #30680
Comments
@Smotrov , thanks for reporting this. Did anything change from your side between successful deployment to failed one ? I mean any packages update or in the code ? Also you mentioned that it is not reproducible so that means it occurred one time ? Could you please share the synthesized template and logs ?? |
normally this error "CannotPullContainerError" would occur in these circumstances as mentioned here in this doc - This sage post might be helpful in further understanding as to why you are getting the error - https://repost.aws/knowledge-center/ecs-task-stopped Let me know if this is helpful. |
Thank you fixed with Docker desktop reset / reinstall. |
|
Comments on closed issues and PRs are hard for our team to see. If you need help, please open a new issue that references this one. |
Describe the bug
I used to deploy my AWS ECS code with CDK with no problem.
All of a sudden yesterday all tasks couldn't start. It shows
Stopped
status with following message on hoverCannotPullContainerError: unsupported media type application/vnd.in-toto+json
.Is it fixable somehow? Now could not deploy anything.
Expected Behavior
Proper deployment
Current Behavior
Can't deploy outdates on ECS
Reproduction Steps
Hard to reproduce
Possible Solution
No response
Additional Information/Context
Before this deployment
cdk deploy --all
randomly fails with following errorRight after this
cdk deploy --all
has no errors except not starting tasks.CDK CLI Version
2.147.1 (build d3695d4)
Framework Version
No response
Node.js Version
v18.20.2
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: