IssueRaiser

Docker does not free up disk space after container, volume and image removal

# Versions & co ## Docker Docker version ``` bash $ docker version Client: Version: 1.8.2 API version: 1.20 Go version: go1.4.2 Git commit: 0a8c2e3 Built: Thu Sep 10 19:19:00 UTC 2015 OS/Arch: linux/amd64 Server: Version: 1.8.2 API version: 1.20 Go version: go1.4.2 Git commit: 0a8c2e3 Built: Thu Sep 10 19:19:00 UTC 2015 OS/Arch: linux/amd64 ``` Docker info: ``` bash $ docker info Containers: XXX Images: XXX Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: XXX Dirperm1 Supported: true Execution Driver: native-0.2 Logging Driver: json-file Kernel Version: 3.19.0-26-generic Operating System: Ubuntu 14.04.3 LTS CPUs: 1 Total Memory: XXX GiB Name: XXX ID: XXXX:XXXX:XXXX:XXXX ``` ## Operating system Linux 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux # Issue Here is how I currently deploy my application: 1. Build a new image based on a new version of my application code 2. Up a new container based on the image created in `1` 3. Remove the previous container and its volume with the command `docker rm -v xxxxx` 4. Remove all the unused images with `docker rmi $(docker images -q)` However, little by little, I'm running out of disk space. I made sure I don't have any orphan volumes, unused containers and images, etc... I found [a post on a forum](http://stackoverflow.com/questions/27853571/why-is-docker-image-eating-up-my-disk-sp

Posted by stouf on Apr 11, 2016, 9:44 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments

github (Sysadmin)

Docker does not free up disk space after container, volume and image removal

stoufApr 11, 2016, 9:44 AM

# Versions & co ## Docker Docker version ``` bash $ docker version Client: Version: 1.8.2 API version: 1.20 Go version: go1.4.2 Git commit: 0a8c2e3 Built: Thu Sep 10 19:19:00 UTC 2015 OS/Arch: linux/amd64 Server: Version: 1.8.2 API version: 1.20 Go version: go1.4.2 Git commit: 0a8c2e3 Built: Thu Sep 10 19:19:00 UTC 2015 OS/Arch: linux/amd64 ``` Docker info: ``` bash $ docker info Containers: XXX Images: XXX Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: XXX Dirperm1 Supported: true Execution Driver: native-0.2 Logging Driver: json-file Kernel Version: 3.19.0-26-generic Operating System: Ubuntu 14.04.3 LTS CPUs: 1 Total Memory: XXX GiB Name: XXX ID: XXXX:XXXX:XXXX:XXXX ``` ## Operating system Linux 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux # Issue Here is how I currently deploy my application: 1. Build a new image based on a new version of my application code 2. Up a new container based on the image created in `1` 3. Remove the previous container and its volume with the command `docker rm -v xxxxx` 4. Remove all the unused images with `docker rmi $(docker images -q)` However, little by little, I'm running out of disk space. I made sure I don't have any orphan volumes, unused containers and images, etc... I found [a post on a forum](http://stackoverflow.com/questions/27853571/why-is-docker-image-eating-up-my-disk-sp

Comments (0)

No comments yet. Start the discussion.

Comment on this issue