Docker Community Forums

Share and learn in the Docker community.

Space used out and never be released

(Bill Wang) #1

Expected behavior

After remove images or container, the space should be released.

Actual behavior

out of space now.


$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34) version v1.11.1-beta13
Running diagnostic tests:
[OK] Moby booted
[OK] driver.amd64-linux
[OK] vmnetd
[OK] osxfs
[OK] db
[OK] slirp
[OK] menubar
[OK] environment
[OK] Docker
[OK] VT-x

Steps to reproduce the behavior

  1. install native docker for mac for one month already, running fine, but this week, got prompt to upgrade to beta 13. then suddenly the disk is out of space (I have 50GB spare space before)
  2. remove all images and container, the docker folder (with big file of Docker.qcow2 and log folder) is used about 70GB, never dropped.

Some logs for your reference:

52 root:~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux
$ du -sk *|sort -n
0	lock
4	mac.0
4	nic1.uuid
4	pid
4	tty
4	xhyve.args
64	console-ring
21475328	log
43805376	Docker.qcow2

$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

58 root:~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

59 root:~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux

63 root:~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/log
$ ls -lctr
total 42950656
-rw-r--r--  1 bill  staff            0  5 May 06:45 wtmp
drwxr-xr-x  2 bill  staff           68 11 May 00:05 rancher
-rw-r--r--  1 bill  staff  13639708672 27 May 11:27 vsudd.log
-rw-r--r--  1 bill  staff       372736 27 May 11:27 proxy-vsockd.log
-rw-r--r--  1 bill  staff       901120 27 May 11:27 messages.0
-rw-r--r--  1 bill  staff    891490304 27 May 11:27 dmesg
-rw-r--r--  1 bill  staff      3096576 27 May 11:27 acpid.log
-rw-r--r--  1 bill  staff         8192 27 May 11:40 messages
-rw-------  1 bill  staff   7455158272 27 May 11:41 docker.log

$ tail -f docker.log
time="2016-05-04T20:45:34.374632523Z" level=debug msg="docker group found. gid: 50"
time="2016-05-04T20:45:34.375018660Z" level=debug msg="Listener created for HTTP on unix (/var/run/docker.sock)"
time="2016-05-04T20:45:34.378436846Z" level=info msg="New containerd process, pid: 1344\n"
time="2016-05-04T20:45:34.380145431Z" level=debug msg="containerd connection state change: TRANSIENT_FAILURE"
time="2016-05-04T20:45:34Z" level=debug msg="containerd: read past events" count=0
time="2016-05-04T20:45:34Z" level=debug msg="containerd: supervisor running" cpus=2 memory=2002 runtime=docker-runc runtimeArgs=[] stateDir="/run/containerd"
time="2016-05-04T20:45:34Z" level=debug msg="containerd: grpc api on /var/run/docker/libcontainerd/docker-containerd.sock"
time="2016-05-04T20:45:35.381288743Z" level=debug msg="Using default logging driver json-file"
time="2016-05-04T20:45:35.382043804Z" level=debug msg="Golang's threads limit set to 14040"
time="2016-05-04T20:45:35.382794447Z" level=debug msg="[graphd^C

There are two problems in fact.

  1. docker disk Docker.qcow2 is keep growing, what ever I clean images/containers or not.

-rw-r–r-- 1 bill staff 44856705024 27 May 11:47 Docker.qcow2

  1. debug is turned on, and generate huge log files

-rw-r–r-- 1 bill staff 13639708672 27 May 11:27 vsudd.log
-rw------- 1 bill staff 7455158456 27 May 11:46 docker.log

(Zach Hanna) #2

I’m observing the same behavior.

OSX 10.11.4 (15E65)
Docker Version 1.11.1-beta13 (build: 7975)

(Rburgst) #4

I would be interested if there is a way to shrink the docker VM disk again. My boot2docker machine had roughly the same amount of stuff in it and was 11GB, docker beta is 30GB, it would be nice to be able to shrink without loosing all the data.