-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Related docker "Thin top" issue #10
Comments
Do you know what version of the ECS agent is running on your machines? I know that newer agents will try to clean up old images, etc: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/automated_image_cleanup.html Might just be a case of trying new AMIs? http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html |
@mhart |
Do you know what version of the ECS agent is running on your machines? Have you tried with one of the newer AMIs? http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html |
I'd like to be able to answer your question but i don't know how :/ I just used the cloud formation cluster.template and defined my Dockerfile.test as shown before :/ |
After several builds, i encountered this problem: http://stackoverflow.com/questions/36918387/space-issue-on-docker-devmapper-and-centos7
And it does block any new ci. I have to delete and recreate the cloud formation stack.
moby/moby#3182 (comment)
The text was updated successfully, but these errors were encountered: