docker-storage-setup fails on F22 cloud image

Lalatendu Mohanty lmohanty at redhat.com
Wed Aug 19 19:35:43 UTC 2015


On 08/20/2015 12:55 AM, Jason Brooks wrote:
>
> ----- Original Message -----
>> From: "Dusty Mabe" <dusty at dustymabe.com>
>> To: cloud at lists.fedoraproject.org
>> Sent: Wednesday, August 5, 2015 7:28:27 AM
>> Subject: docker-storage-setup fails on F22 cloud image
>>
>>
>> docker-storage-setup fails on our cloud image because there is no storage for
>> it
>> to configure. In my case I am just testing on openstack with no ephemeral
>> disks
>> attached to the instance.
>>
>> All you need to do to show this is install and start docker and then
>> you will see:
>>
>> [root at f22 ~]# systemctl status docker-storage-setup
>> ● docker-storage-setup.service - Docker Storage Setup
>>     Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service;
>>     disabled; vendor preset: disabled)
>>     Active: failed (Result: exit-code) since Wed 2015-08-05 14:15:14 UTC; 4min
>>     3s ago
>>    Process: 6951 ExecStart=/usr/bin/docker-storage-setup (code=exited,
>>    status=3)
>>   Main PID: 6951 (code=exited, status=3)
>>
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: WARNING: Failed to connect to
>> lvmetad. Falling back to internal scanning.
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: Metadata volume
>> docker-poolmeta already exists. Not creating a new one.
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: /run/lvm/lvmetad.socket:
>> connect failed: No such file or directory
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: WARNING: Failed to connect to
>> lvmetad. Falling back to internal scanning.
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: Please provide a volume group
>> name
>> Aug 05 14:15:14 f22 docker-storage-setup[6951]: Run `lvcreate --help' for
>> more information.
>> Aug 05 14:15:14 f22 systemd[1]: docker-storage-setup.service: main process
>> exited, code=exited, status=3/NOTIMPLEMENTED
>> Aug 05 14:15:14 f22 systemd[1]: Failed to start Docker Storage Setup.
>> Aug 05 14:15:14 f22 systemd[1]: Unit docker-storage-setup.service entered
>> failed state.
>> Aug 05 14:15:14 f22 systemd[1]: docker-storage-setup.service failed.
>>
>>
>> Should we fix this so that there isn't a failed unit if there is no storage
>> to configure?
> Can we do something like -- don't try to run unless there's an uncommented
> line in docker-storage-setup... ?
>
> Jason

Interestingly we are seeing something similar in CentOS based box [1] . 
But looks like fixable through the kickstart file.

[1] https://github.com/projectatomic/adb-atomic-developer-bundle/issues/69
>
>
>> Dusty
>> _______________________________________________
>> cloud mailing list
>> cloud at lists.fedoraproject.org
>> https://admin.fedoraproject.org/mailman/listinfo/cloud
>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>>
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct



More information about the cloud mailing list