vinayan3
(Vinayan3)
June 6, 2016, 3:43pm
1
Expected behavior
The .qcow2 not to be so large
Actual behavior
The .qcow2 file is 33.3gb last week it was around 20GB. It seems to grow.
Information
I read in another post it’s storing stuff which goes to volumes? Is there anyway that I can inspect whats stored in there and clean it up?
2 Likes
Mine is 15Gb but growing too
It’s going to keep growing unless you clean up your unused docker images/containers/volumes
docker rm $(docker ps -q -f ‘status=exited’)
docker rmi $(docker images -q -f “dangling=true”)
docker volume rm $(docker volume ls -q -f ‘dangling=true’)
The volumes one is dangerous if your active stack isn’t running in docker.
vinayan3
(Vinayan3)
June 10, 2016, 4:59pm
4
I have run the commands and the size has dropped. I am reading on another thread .qcow2 free space can’t be reclaimed therefore it’ll continue to grow. The comment on that is here:
Hi @chrisevens, It’s possibly because the Docker.qcow2 is full.
Can you try ls -lah ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2?
The disk is a 64GB Sparse Image that will expand on demand… We currently aren’t able to reclaim unused space but we’ll hopefully have a fix in a future beta. You can delete this file providing you aren’t worried about loosing any containers/images, and restart Docker. This should get you back on track.
Let me know if this h…
pcas
(Paul Cassidy)
August 8, 2016, 6:21pm
5
Is there an issue to track for this? I’m having to delete my Docker.qcow2 every couple weeks at this point.
1 Like
jpgorman
(Jpgorman)
September 28, 2016, 3:34pm
6
Can’t tell you how much time I have wasted on successive docker image screw ups this year. Releasing this even in a beta without the ability to expand and contract the image to required size is just beyond belief.