> The containerd image store uses more disk space than the legacy storage drivers for the same images. This is because containerd stores images in both compressed and uncompressed formats, while the legacy drivers stored only the uncompressed layers.
Why ?
It is shameful for apple to hard solder their disks. There is no benefit to the user
As we have seen with framework even the hard solder ram is not needed to get reasonable performance. At least let me expand my memory even if it doesn't perform as fast as on chip.
Actually, it is. The speed and latency difference does matter, that is how even an 8GB RAM MacBook feels snappier than many a 32GB Windows machine - it can use the disk as swap.
If you believe the latest M3 does not perform better than machines you’ve used in the 80s, I have no idea how to even start a reasonable discussion about this.
This seems like a really weird decision. If base images are duplicated for every image you have, that will add up quickly.
docker system prune -a -f
docker volume prune -a -fRef: https://docs.docker.com/reference/cli/docker/system/prune/
neitsab•3d ago
This means `/var/lib/docker` is no longer "hermetic": images and container snapshots are located in `/var/lib/containerd` now.
More info about the switch: https://www.docker.com/blog/docker-engine-version-29/
To configure this directory, see https://docs.docker.com/engine/storage/containerd/.
neitsab•3d ago
To keep both /var/lib/{containerd,docker} in sync, I use a single ZFS dataset ("custom filesystem volume" in Incus parlance) and mount subpaths inside the container:
There are other ways to achieve the same of course.