1. Carbon Copy Cloner

When I ran my Docker container with the Mac disk image mounted as a volume, the make process failed because it created many files of apparently the right size, but filled with 0x00. Changing to a sparse image didn't help, but it seems to work when I created a.dmg file with the total amount pre-allocated by Disk Utility.

The current state is: • on edge 18.05.0-ce-mac67 we default to Docker.raw on macOS 10.13.4 (and later) running on APFS, otherwise we use Docker.qcow2 • on stable 18.03.1-ce-mac65 we default to Docker.qcow2. The next version of stable will default to Docker.raw on macOS 10.13.4 (and later) running on APFS. Note that APFS (needed by Docker.raw) is not supported by all Apple hardware.

$ docker history bd09118bcef6 IMAGE CREATED CREATED BY SIZE COMMENT bd09118bcef6 4 minutes ago /bin/sh -c #(nop) COPY dir:35a7eb158c1504e. 100B 31005225a745 3 months ago /bin/sh -c #(nop) CMD ['/bin/bash'] 0B 3 months ago /bin/sh -c mkdir -p /run/systemd && echo '. 7B 3 months ago /bin/sh -c sed -i 's/^# s * (deb.

Signed-off-by: David Scott. The disk space usage of Docker on Mac has been difficult to manage and has confused lots of people, see This patch adds a top-level section to the Docker for Mac docs alongside networking which explains - where the space has gone - how to reclaim some of it In future I'd like to add more about why some systems use `Docker.raw` and some `Docker.qcow2` but we're in a transitional state at the moment. It'll be simpler to explain after the next stable version has been released. Signed-off-by: David Scott. • I just wiped all of my data and upgraded to Docker for Mac 18.06.0-ce-mac70, enabling the raw format by default.

Re-enable raw as the the default disk format for users running macOS >>>10.13.4 and higher>>“reset to factory defaults” or “remove all data” Preferences -> Reset). Related to About the reference to the fix; docker is closed source so you won't see a commit link here. I assume the docker team will resolve this one once the fix makes its way to stable.

Download openstreetmap-carto to a local subdirectory of the user’s home directory (C: users username): cd git clone cd openstreetmap-carto Download a PBF of OSM data to the same directory where openstreetmap-carto has been downloaded, as mentioned in. The downloaded file shall be named data.osm.pbf. Eval $(docker-machine env default) To totally remove the docker installation, delete the virtual machine named default ( docker-machine rm default) and the directory C: Users.docker. While docker-compose up is running, the openstreetmap-carto development can be directly done on the PC by accessing the local directory where openstreetmap-carto has been downloaded. E.g., locally editing a stylesheet and then pressing the Kosmtik Reload button on the browser, the map gets updated.

It seems that when APFS allocates blocks for sparse files, they can occasionally end up with corrupt contents. I suspect the bug has been fixed on the macOS developer beta (10.13.4) recently and I hope the fix will be released as a regular update soon. In the meantime we've switched back to qcow2 by default for safety. When we're convinced the underlying bug has been fixed we'll switch back to raw again. Thanks all (especially for the test case). I confirmed the bug still reproduces on my 10.13.3 machine and then updated to 10.13.4.

Office 365 mac compatibility. Sorry for all of the comments, trying to give as much info as I can since this is a pretty unpredictable bug. Could this be related to an issue that I am seeing with mounting volumes?

By default, the disk image is stored in ~/Library/Containers/com.docker.docker/Data/vms/0. Qcow2 or Raw? Starting with High Sierra with Apple Filesystem (APFS) enabled, Docker uses disk images in the “raw” format ( Docker.raw), otherwise in the Qcow2 format ( Docker.qcow2). Docker.raw consumes an insane amount of disk space! This is an illusion.

Carbon Copy Cloner

After running Docker for Mac for a long time, Docker keeps eating up disk space. Even though the containers and images are removed, the disk space is not reclaimed. The problem is the file /Users//Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 is too big.