Docker 1.7.0 is using huge amount of disk space

Hi, I have problem on disk space usage on 1.7.0. I have >800 MB image build with 1.6.2.

If I launch Ubuntu 14 EC2 instance and install Docker 1.6.2, total disk usage after pulling my image is 2 GB.

If I launch Ubuntu 14 EC2 instance and install Docker 1.7.0, total disk usage after pulling my image is 32 GB. What can cause this?

Unfortunately image on question is on private repo and I can’t share it.

I’m having the same problems with our public images.

If you pull down the “enonic/java8” image it eats up 5gb of disk alone, while on docker 1.6.2 it uses 1GB

Both servers are identical setup with the same cloud init file and I’m using the official ubuntu 14.04.2 LTS cloud images on a set of openstack instances to run docker on.

Docker file: https://github.com/enonic/docker-xp/blob/master/docker-java8/Dockerfile

We faced the same problem, like you have described.
We run docker pull repo/image and it takes 39 GB, when disk size is 40GB.
Ubuntu 14.04, docker 1.7.0, images are in docker hub.
After I terminate pulling, docker service takes 40-50% cpu.
I will create an issue in github.

Reason seems to be missing aufs settings on install script https://get.docker.com/ubuntu/ that I used for installing Docker so devicemapper is used. And for some reason devicemapper uses lots of space on 1.7.0.

Works fine when installed docker with https://get.docker.com script.

The problem seems to be that docker is not using the right storage driver.
Run docker info and you’ll see Storage Driver: vfs

If you install the linux-image-extra package of your current kernel and reinstall docker, aufs support will be enabled and the issue will be fixed.

sudo apt-get remove lxc-docker
sudo apt-get autoremove
sudo apt-get install -y linux-image-extra-$(uname -r)
sudo apt-get install -y lxc-docker

If you run docker info now, you should see Storage Driver: aufs

Here’s a gist that installs docker, docker-compose and a docker-cleanup script: https://gist.github.com/wdullaer/f1af16bd7e970389bad3

An alternative method is to install docker from source with support for aufs or devicemapper, as explained here: http://icarobichir.com.br/posts/building-a-dynamically-linked-docker-v-1-6-2/

Here is a great presentation from @jpetazzo about Docker storage drivers if you want to know more about them: https://jpetazzo.github.io/assets/2015-03-03-not-so-deep-dive-into-docker-storage-drivers.html#1