On 12/12/2016 05:19 PM, Jason Brooks wrote: > On Mon, Dec 12, 2016 at 2:12 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: >> After I get a bug[1] fixed and out the door I'm going to publish >> a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud >> base to use overlay2 as the storage driver for docker. >> >> I'd like for everyone that can to test this out and to start running >> their container workloads with overlay2 with selinux enabled and let's >> file bugs and get it cleaned up for Fedora 26 release. > This makes sense as the default for the docker package for non-atomic > fedora, since the alternative is loopback storage -- are you > suggesting this as a change for the atomic host as well? If so, what's > the rationale there? Overlay allows better memory sharing, so you can run more containers on a single host then you can with Devicemapper. We are working on patches to docker-storage-setup to allow it to allocate overlayfs to the remaining storage similar to what we do with devicemapper for Atomic Host. >> Should we file this as a "change" for Fedora 26? >> >> Dusty >> _______________________________________________ >> cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx