-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Deprecate AUFS? #1326
Comments
Ok, let's do this. Release notes for 18.06.x officially updated: https://github.com/boot2docker/boot2docker/releases/tag/v18.06.0-ce I'm going to leave this issue open for a bit as a catch-all to hopefully provide slightly better visibility for this change. |
So far changing /var/lib/boot2docker/profile to overlay2 No issues loading an image and attaching a container. Question. How does /var/lib/boot2docker/profile get created in a newly created vm. Does that come from docker-machine? docker@kernel-414:~$ docker info |
Yeah, likely; is it embedding AUFS explicitly there? We might also have
some code preferring AUFS we need to adjust.
|
docker@default:~$ cat /var/lib/boot2docker/profile EXTRA_ARGS=' ' |
https://github.com/docker/machine/blob/master/libmachine/provision/boot2docker.go
This default will need changing. |
Thanks for the digging / info @kaosagnt! ❤️ I've filed docker/machine#4558 to discuss/update those references. 👍 |
Most likely, the same change should go into Minikube (even though it doesn't use Boot2Docker by default) https://github.com/kubernetes/minikube/blob/master/pkg/minikube/machine/client.go#L113 EngineOptions: &engine.Options{
StorageDriver: "aufs",
TLSVerify: true,
}, |
This was changed in Minishift already, although they went from "devicemapper" to "overlay2": Mostly because devicemapper falls back to "loopback" unless drives are partioned correctly... https://github.com/minishift/minishift-centos-iso
|
The latest release of Docker for Windows ("Docker Community Edition 18.06.0-ce-win70 2018-07-25") has officially deprecated AUFS with the following notice (https://docs.docker.com/docker-for-windows/release-notes/#docker-community-edition-18060-ce-win70-2018-07-25):
I'm thinking it's probably sane for us to follow suit and have 18.06.x be the final release that supports AUFS (especially since it repeatedly makes kernel upgrades / choosing a kernel version challenging).
The text was updated successfully, but these errors were encountered: