Docker doesn't release disk space used by `~/Library/Containers/com.docker.docker/`

Expected behavior

When removing all images, disk space is released

Actual behavior

Disk space is not released

Information

$ pinata diagnose -u
OS X: version 10.11.5 (build: 15F34)
Docker.app: version: v1.11.1-beta14.5.m
Running diagnostic tests:
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160610-181502.tar.gz
Most specific failure is: No error was detected
Your unique id is: 07F54247-13B0-442B-887D-C75E7A3B89FA
Please quote this in all correspondence.

Steps to reproduce the behavior

Add some images, remove all images with docker images -q |xargs docker rmi --force

I filed a bug here: https://github.com/docker/docker/issues/23437

Anybody knows if there’s a better solution than to kill the Docker installation by deleting ~/Library/Containers/com.docker.docker?

I have to remove that once every 2 or 3 days and setup all images again to prevent it growing larger than 30GB.

Thanks

The same problem, docker doesn’t release disk space.
Anybody knows how to move images to external hard drive?

diagnostic id FB9F95D1-0EFD-47BA-BABF-87ED0D3DA813
Docker for Mac: version: mac-v1.12.0-beta16.2
OS X: version 10.11.4 (build: 15E65)
logs: /tmp/20160621-150923.tar.gz
failure: No error was detected
[OK] docker-cli
[OK] app
[OK] menubar
[OK] virtualization
[OK] system
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

1 Like

Resetting to factory defaults works for me. You can do this through the menu bar helper.

I just used the reset to factory default and reclaimed about ~60 of 500 GB of disk space even though I have a moderate/low docker usage…

1 Like

Since the original GitHub issue linked in the OP is closed, here’s the new issue for this: https://github.com/docker/for-mac/issues/371

i used this solution to resolve the disk issue