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
devicemapper leaking #746
Comments
@cjbottaro DeviceMapper is the default storage driver on ECS Optimized AMI. We choose devicemapper as the default storage driver based on our qualification, because it is more stable than the other alternatives. You can change that by configuring Docker with the overlay/overlay2 storage driver following the instruction here. On ECS Optimized AMI you need to run Thanks, |
Ok. For posterity, here's the bash script I used to do this. I made an AMI out of the results. https://gist.github.com/cjbottaro/394bcf05deb83892a6bb2a7f4914e227 The AMI I used as a starting point is ami-a98cb2c3. |
This PR & gist were very helpful in moving our ECS agents to overlay2 -- thanks! FWIW, we did this purely in user-data so that we could just keep using the official ECS AMI.
|
with the latest ami this still is an issue ; creating / removing files inside a container does not free the files until the containers are removed. So touch > bigfile , rm bigfile makes docker info report an increasing number. |
Hi.
Seeing containers fail with this message:
Seems to be an issue with devicemapper:
moby/moby#18867
moby/moby#3182
Here's some info about my instance:
I'm using the latest ECS optimized AMI (the one with the letter
g
in it).Is it possible for the next AMI to use the overlay fs and overlay2 driver?
Thanks.
The text was updated successfully, but these errors were encountered: