ISO installs of f23 atomic get configured w/ loopback storage, which is a bad thing: http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/.
F22 Atomic had the correct config.
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-x86_64-22.iso yields:
{{{ ... Storage Driver: devicemapper Pool Name: fedora-docker--pool Pool Blocksize: 65.54 kB Backing Filesystem: extfs Data file: Metadata file: ... }}}
Running "docker info" on a VM installed from Fedora-Cloud_Atomic-x86_64-23.iso yields:
{{{ ... Storage Driver: devicemapper Pool Name: docker-253:0-153054-pool Pool Blocksize: 65.54 kB Backing Filesystem: extfs Data file: /dev/loop0 Metadata file: /dev/loop1 ... }}}
I looked over the kickstarts, but I'm not clear on what might be causing this.
https://github.com/projectatomic/fedora-productimg-atomic is responsible for setting this up correctly. There's a bug (https://bugzilla.redhat.com/show_bug.cgi?id=1290257) and pending fixed pkg pending... not sure if it'll fix this issue as well.
This pkg fixes my issue: https://bodhi.fedoraproject.org/updates/FEDORA-2015-1b6b8653f0
You can test w/ https://bugzilla.redhat.com/show_bug.cgi?id=1290257#c4 and give it karma
Looks good here too. Assuming this gets pulled in for the two-week due next week, we're good. Woot.
Login to comment on this ticket.