![Mac Mac](/uploads/1/2/5/4/125497994/506706634.png)
This is becoming really really annoying. I think at the very least you should expose a config setting where one can set the directory location to another disk. And even better would be if the big images files were actually hosted and visible on the Mac, so one can manually remove a file or two when the docker machine doesn’t start up again.
So basically mount the files into the docker machine like a shared file system. If that is technically not possible, then mount the directory where the big files are on the docker machine to a directory on the mac host, so if and when the docker starts up again, one can go and remove files that are no longer required, without having to throw away the whole gcow2 file and start all downloads all over again. About out of disk space, has anyone even seen something like this? We are using Docker 1.12.1 on our Jenkins slaves vApps in our CI infrastructure.
We have a problem. Could you support us to explain what’s happen?
Thanks in advance. Our main question is to know why docker-compose creates and keep images with that strange name, concatenating previous to the base image name such set of Ids. Problem Description: Jenkins job suffer of really frequent container name corruption (1 every 4 run). Docker ps show weird container (holding resource) like: ff3acbffe419ff3acbffe419ff3acbffe419ff3acbffe419ff3acbffe419dockerjboss1 or 8b2b1935d74e8b2b1935d74edockerjboss1 and removing those containers jobs is working fine. Logs with faulty container are attached. Made a preliminary inspection on faulty Vapp (JenkinsFem108DockerSlave12): root@atvts3354 docker# docker-compose ps Name Command State Ports 8b2b1935d74e8b2b1935d74e8b2b1935d74edockerjboss1 /bin/sh -c sleep 20 && cp Exit 128 dockerdpsintegration1 /bin/sh -c /usr/sbin/xinet Up 5019/tcp dockerjboss1 /bin/sh -c cp /opt/ericsso Exit 128 dockerpostgres1 /docker-entrypoint.sh postgres Up 5432/tcp jboss has 2 different “images” one looks corrupted as in description, in addition also State Exit 128 could be investigated.
When running out of disk space, because of the size of the Docker.qcow2 file, the only reliable solution is to delete this file and start with an empty VM image (stop Docker for Mac, delete the file, then restart Docker for Mac). How to claim free space generated by deleting docker images in Mac. How can I reclaim the freed space occupied by virtual box image. I am using Mac Yosemite.
I've been searching for a while, but couldn't find a way to analyze the disk usage of a Docker container / volume. I can see that Docker takes 12GB of my filesystem: 2.7G /var/lib/docker/vfs/dir 2.7G /var/lib/docker/vfs 2.8G /var/lib/docker/devicemapper/mnt 6.3G /var/lib/docker/devicemapper/devicemapper 9.1G /var/lib/docker/devicemapper 12G /var/lib/docker But, how do I know how this is distributed over the containers? I tried to attach to the containers by running (the new v1.3 command) docker exec -it bash and then running 'df -h' to analyze the disk usage. It seems to be working, but not with containers that use 'volumes-from'. For example, I use a data-only container for MongoDB, called 'mongo-data'. When I run docker run -it -volumes-from mongo-data busybox, and then df -h inside the container, It says that the filesystem mounted on /data/db (my 'mongo-data' data-only container) uses 11.3G, but when I do du -h /data/db, it says that it uses only 2.1G.
So, how do I analyze a container/volume disk usage? Or, in my case, how do I find out the 'mongo-data' container size?