On 12/10/2015 03:39 AM, Chris Murphy wrote: > OK instead of hijacking some other thread...(sorta too late). > > # lsblk -f > NAME FSTYPE LABEL UUID > MOUNTPOINT > sda > =E2=94=9C=E2=94=80sda1 vfat 5956-63D8 > /boot/efi > =E2=94=9C=E2=94=80sda2 btrfs f23a > 8b0c4840-4fc7-4782-a4c0-25fec8a40dd4 /sysroot > =E2=94=9C=E2=94=80sda3 ext4 > 908cb4df-410b-47e4-afb1-872255bd1244 /boot > =E2=94=9C=E2=94=80sda4 LVM2_member > 9WkBEW-XwcN-8f99-nQOP-E1w8-QiBs-6Xio7a > =E2=94=94=E2=94=80sda5 swap > 53f95874-06db-4433-a74b-8dc31105c528 [SWAP] > > -bash-4.3# pvs > PV VG Fmt Attr PSize PFree > /dev/sda4 VG lvm2 a-- 426.51g 126.36g > -bash-4.3# vgs > VG #PV #LV #SN Attr VSize VFree > VG 1 1 0 wz--n- 426.51g 126.36g > -bash-4.3# lvs > LV VG Attr LSize Pool Origin Data% Meta% Move > Log Cpy%Sync Convert > docker-pool VG twi-a-tz-- 300.00g 0.00 0.44 > So you created the VG VG and the docker-pool LV on your own before docker-storage-setup is run? What I would do is leave sda4 blank and then put the following in your config file: DEVS=/dev/sda4 VG=vgdocker What I think this will do is create a PV out of /dev/sda4 and create a VG (named vgdocker) on top of it. It will then create the docker-pool LV for you and have the docker daemon use that as the backing store. Let me know if this is what you were looking for or not! Dusty _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
