On Mon, Dec 12, 2016 at 2:24 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > > > 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? >> > > I think the rationale is that we'd like to not have a much different > experience whether you are using docker on atomic host or not. My > thoughts are that overlay is where we want to be in the future and > Fedora is the first place we should try that out. It's a matter of choosing harmonization on non-atomic and atomic fedora at the cost of harmonization between centos/rhel/fedora atomic hosts, so there's gain and loss there, but if overlay is where we want to be in the future (I assume "we" is Red Hat?) it makes sense to get on with it. > > DM would still be supported via configuration of docker-storage-setup, > just like overlay is supported today in the same way. > > Thoughts? > > Dusty > _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
