I created a thin poll storage volume using the helper script "container-storage-setup".
Here is my /etc/sysconfig/docker-storage-setup ------------------------- VG=vg-docker ROOT_SIZE=+100%FREE MIN_DATA_SIZE=8G GROWPART=true POOL_AUTOEXTEND_PERCENT=10 ---------------------- NOTE: default driver is devicemapper in "/usr/share/container-storage-setup/container-storage-setup", exactly what I am looking for. After running the script, here is part of docker info: ------------------- # docker info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 17.03.2-ce Storage Driver: overlay2 Backing Filesystem: xfs ..... ------------------------- As you can see, driver is set to overlay2 when I was expecting devicemapper. NOTE: Filesystem is good, xfs, but I don't know where does this filesystem comes from as I didn't format the partition. Did the script do it? when running lsblk, i can see this: ----------------------------- # lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sr0 iso9660 config-2 2018-05-30-00-18-35-00 vda ├─vda1 ext4 8eb202fa-c75c-43f6-9a87-7ddb013ce0fa /boot └─vda2 LVM2_member Ji8MSG-yiKd-ZSlF-cop0-siUg-SPSN-xMhEkx └─atomicos-root xfs 854965bc-06ad-40df-af9d-7bfb318c1aed /sysroot vdb └─vdb1 LVM2_member Wblg0x-nsLd-1eyE-sZfA-jQfO-Ldvi-rUGdK1 ├─vg--docker-docker--pool_tmeta │ └─vg--docker-docker--pool └─vg--docker-docker--pool_tdata └─vg--docker-docker--pool ---------------------- As you can see, there is no shown filesystem for my docker pool . Why? Now, looking at /etc/sysconfig/docker-storage: -------- # cat /etc/sysconfig/docker-storage DOCKER_STORAGE_OPTIONS="--storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/vg--docker-docker--pool --storage-opt dm.use_deferred_removal=true --storage-opt dm.use_deferred_deletion=true " ----------------- Here it shows my storage driver as set to devicemapper ! So, what is exactly my storage driver, as bot command don't return the same value. Thank you for help/explanations.
