On Wed, Dec 9, 2015 at 12:26 PM, Fedora Cloud Trac Tickets <cloud-trac@xxxxxxxxxxxxxxxxx> wrote: > #144: f23 atomic iso configures docker loopback storage > I looked over the kickstarts, but I'm not clear on what might be causing > this. > Ticket URL: <https://fedorahosted.org/cloud/ticket/144> I'm replying to list to avoid cluttering the ticket. I'm in the vicinity of a related issue, trying to figure out what's doing the setup, because I didn't use the prescribed automatic partitioning layout, therefore don't have any lvmthinp stuff setup yet. The ISO seems to create a system that's somehow making assumptions, but I don't know where it's getting that info. For example, I'm running into this: ● docker-storage-setup.service loaded failed failed Docker Storage Setup ● docker.service loaded failed failed Docker Application Container Engine The cause for storage setup service failing is Dec 09 16:57:46 f23a.localdomain docker-storage-setup[759]: Volume group "sda2" not found Dec 09 16:57:46 f23a.localdomain docker-storage-setup[759]: Cannot process volume group sda2 Dec 09 16:57:46 f23a.localdomain docker-storage-setup[759]: Metadata volume docker-poolmeta already exists. Not creating a new one. Dec 09 16:57:46 f23a.localdomain docker-storage-setup[759]: Please provide a volume group name Dec 09 16:57:46 f23a.localdomain docker-storage-setup[759]: Run `lvcreate --help' for more information. But where is it thinking there'd be a VG called sda2? OK so I do [chris@f23a ~]$ cat /usr/lib/systemd/system/docker-storage-setup.service [Unit] Description=Docker Storage Setup After=cloud-final.service Before=docker.service [Service] Type=oneshot ExecStart=/usr/bin/docker-storage-setup EnvironmentFile=-/etc/sysconfig/docker-storage-setup [Install] WantedBy=multi-user.target That suggests looking at /etc/sysconfig/docker-storage-setup, which does not exist (yet?). I also don't know the significance of the - right after = in that line. There is a /etc/sysconfig/docker-storage file that contains: # This file may be automatically generated by an installation program. # By default, Docker uses a loopback-mounted sparse file in # /var/lib/docker. The loopback makes it slower, and there are some # restrictive defaults, such as 100GB max storage. # If your installation did not set a custom storage for Docker, you # may do it below. # Example: Use a custom pair of raw logical volumes (one for metadata, # one for data). # DOCKER_STORAGE_OPTIONS = --storage-opt dm.metadatadev=/dev/mylogvol/my-docker-metadata --storage-opt dm.datadev=/dev/mylogvol/my-docker-data DOCKER_STORAGE_OPTIONS= So it might be that the Fedora 23 Atomic ISO behavior is the result of upstream behavior, and Fedora 22 had a modifier that no longer exists in Fedora 23? -- Chris Murphy _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
