You can then run docker info again to see what has been cleaned up docker infoĪlong with this, make sure your programs inside the docker container are not writing many/huge files to the file system.Ĭheck your running docker process's space usage size docker ps -s #may take minutes to return
(Next time you run a container it may pull from the Docker registry)Įxample output: Total reclaimed space: 1.243GB It will show you a warning that it will remove all the stopped containers,networks, images and build cache. The following commands from the issue clear up space for me and it's a lot safer than deleting /var/lib/docker or for Windows check your disk image location here.Ĭommand in newer versions of Docker e.g. Operating System: Amazon Linux AMI 2014.09ĭeleting my entire /var/lib/docker is not ok for me. Metadata file: /disk1/docker/devicemapper/devicemapper/metadata After I removed some docker images, /dev/xvda1 has some more extra space now.ĭata file: /disk1/docker/devicemapper/devicemapper/data
I can verify this problem by remove some docker images. The problem is that when I continue download docker images and run docker containers, it seems that the other hard drive /dev/xvda1 is also used up. Note that /disk/1 is using a completely different hard drive /dev/xvdi Filesystem Size Used Avail Use% Mounted on I have setup docker and I have used completely different block device to store docker's system data: /]# cat /etc/sysconfig/docker
0 kommentar(er)
