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
Docker keeps taking more storage space under C:\ProgramData\docker\windowsfilter with no way to reclaim it since prune commands not available #688
Comments
@paylocity-sflanders you're using an old version of Docker that doesn't support
If all else fails, have a look at this: https://github.com/jhowardmsft/docker-ci-zap But know that it's very dangerous and very unsupported. |
Closing, but please re-open if this doesn't get you unstuck. |
I'm noticing different behavior if running the same version on windows server 2016 and windows 10. On server it doesn't appear to cleanup the same amount of stuff. In this example i run the same command to delete the image, prune and then pull again. You will see on windows 10 it had to download several more layers than on server 2016, so it has the appearance that some of the layers don't get removed.
Windows Server 2016 Standard (1607, 14393.447)
Windows 10 Enterprise (1607, 14393.1066)
|
I can't reopen this, so created new ticket and linked to this one. The new one is: #745 |
hi @paylocity-sflanders , Can I ask what script you have to get these results?
|
I've experienced the same behavior (images remaining on disk even after |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
Drive space grows and shrinks as you add and remove things and cleanup orphaned data.
Actual behavior
With no images or containers installed we are seeing 30+ gigs of files under C:\ProgramData\docker\windowsfilter. It appears to be caching things that i explicitly removed.
Information
We have been working on some docker images where we are constantly running the build command. We have a helper script that handles cleaning up unused data but it only cleans up part of it. The C:\ProgramData\docker\windowsfilter folder just keeps growing and we have to continually fight running out of drive space. The only solution i'm seeing now is to completely uninstall docker and reinstall, but thats not an option if we use this in production. We need reliable way to manage storage usage in docker for it to be viable.
Windows Server 2016 DataCenter, Version 1607, OS Build 14393.447
Is there any workarounds to cleanup unused docker artifacts? The prune command seem to help with this but they don't appear to be available on windows server 2016, only windows 10.
docker system prune
docker container prune
docker image prune
docker network prune
docker volume prune
Steps to reproduce the behavior
Simply interacting with docker by building and running images seems to continually add data to C:\ProgramData\docker\windowsfilter. Below is more information on what we are seeing in our environment
Images Before
Containers Before
Volumes Before
Docker Folders Before
Then we deleted all the images and expected to see a great reduction in storage, but it was only reduced partially
Docker Folders After
Pulling images i just removed are still on the box
Docker Info
Docker version
Output from Debug-ContainerHost.ps1
Cleanup script
The text was updated successfully, but these errors were encountered: