My apologies if I wasn't clear on my email.
>> Since b0e74fc3888e ("switch to overlayfs as backend"), docker-upstream
>> started to use overlayfs instead of AUFS.
I mean ClearLinux docker-upstream package:
> That's the default choice but I assume AUFS is still
I'll keep AUFS kernel drivers on Clear Linux LTS version
(note - still chatting internally - but we can take/start this chat
off-list - I'd be happy to see that to check our external list is working etc.)
What external list?
* Clear Linux ML <dev(a)lists.clearlinux.org> <-- I will post a comment.
* Clear Containers ?? <-- Do we have a external ML?
That's my presumption from reading around the Docker links. I
don't have a local git clone of Docker, and could not find that commit easily on the
github web interface (I probably could if we had a full commit id) - a link to the webpage
for the commit might be useful here.
My apologies, I mean our local docker-upstream package.
>> What gave this change was:
>> Linux kernel will stop supporting AUFS.
> Are we sure we no longer want to support users that somehow expect
> AUFS to be available ?
Presuming we are talking ClearLinux Kernel (as we cannot speak for all the other distros
- where I expect aufs would hang around for quite some time?) - I would presume we would
include all the FSs that Docker supports, and not just the default one they choose for the
I followed some links off the pages you shared (good links btw) - and found this page
helpful for an overview of the Docker FS world:
Yes, ClearLinux kernel.
I'll remove AUFS from native, KVM & Hyper-V and keep them on LTS.
> On a side note, please post this kind of information to the public
> mailing list from now on.