IssueRaiser

[ECS] [Deployment]: ECS deployment circuit breaker should deal with exceptional exit container

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** What do you want us to build? Use Cloudformation to update ECS background task **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** As the demo of [*Deployment circuit breaker*](https://aws.amazon.com/cn/blogs/containers/announcing-amazon-ecs-deployment-circuit-breaker/), the container start failed with error: `docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"exit\": executable file not f

Posted by forward2you on Dec 24, 2020, 11:16 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

github (Software)

[ECS] [Deployment]: ECS deployment circuit breaker should deal with exceptional exit container

forward2youDec 24, 2020, 11:16 AM

<!-- Please keep this note for the community --> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **Tell us about your request** What do you want us to build? Use Cloudformation to update ECS background task **Which service(s) is this request for?** ECS **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** As the demo of [*Deployment circuit breaker*](https://aws.amazon.com/cn/blogs/containers/announcing-amazon-ecs-deployment-circuit-breaker/), the container start failed with error: `docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"exit\": executable file not f

Comments (0)

No comments yet. Start the discussion.

Comment on this issue