Amogh Rathore
Amogh Rathore
Only v4 endpoint's response may be changed. Older versions are considered immutable. Need to limit this change to v4.
Are we adding prebuilt pause containers to optimize for speed? Should we update the description with the motivation for these changes?
I get this error on CircleCI. I am assuming that it's due to encrypted file system but it only occurs where I use pickling so I think it still qualifies...
Closing this due to lack of activity. @thiagoscodelerae please reopen if you are still facing issues and can provide us logs from you container instance.
Hi @zahorniak . In addition to the information shared by @mye956 above, the following two configuration options might be useful for you use case. Have you tried these already? ---...
> ECS Agent wrongly tells that EC2 has available resources from the stopped container, but it's still active and running in real life. Also on this point, ECS Agent does...
Hi @mliezun. Thanks for creating this issue and sorry for the delay in our response. I will move transfer this issue to our feature requests repository.
Thank you for the feature request, @paologallinaharbur. I will move the request to https://github.com/aws/containers-roadmap/issues which is our central feature request tracking repository.
We released a permanent fix for this issue in https://github.com/aws/amazon-ecs-agent/releases/tag/v1.82.3. Please reopen the issue if you see it again. :) Thank you!
Fixed in https://github.com/aws/amazon-ecs-agent/pull/3987