I don't think it would be a problem, just that when changing versions, the configuration files (daemon.json) will not be in /etc/sysconfig/docker* . You will probably have to change the options for the docker daemon in /etc/docker and another directory. This is where you can change the driver for lvm, etc.
2018-06-05 12:02 GMT+02:00 arnaud gaboury <arnaud.gabo...@gmail.com>: > > > On Tue, Jun 5, 2018 at 11:53 AM arnaud gaboury <arnaud.gabo...@gmail.com> > wrote: > >> On Tue, Jun 5, 2018 at 10:18 AM Carmelo Zubeldia Matute < >> czubel...@intellimentsec.com> wrote: >> >>> I think you are not using the docker-ce version that comes with atomic. >>> You can send the result of the command: >>> >>> rpm -qa | grep -i docker >>> >> >> 611:docker-ce-17.03.2.ce-1.el7.centos.x86_64 >> >> Yes you are right, I had to use an older version as my machines will be >> part of Kubernetes cluster and not all docker versions are compatible. This >> could in fact explain my issue, as I already spent many hours using various >> methods (manually, helper script, various settings) and can't extend the >> atomic root with my volume. >> > > In fact, looking at various matrix, I think I can use other version. I > need to respect the version needed by Rancher as I will use this management > tool. > >> >> >> >>> Thanks, >>> >>> 2018-06-01 15:06 GMT+02:00 arnaud gaboury <arnaud.gabo...@gmail.com>: >>> >>>> 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. >>>> >>>> >>>> >>> >>> AVISO DE CONFIDENCIALIDAD. Este mensaje se dirige exclusivamente a su >>> destinatario y puede contener información privilegiada o CONFIDENCIAL. Si >>> no es Vd. el destinatario indicado, queda notificado de que la utilización, >>> divulgación y/o copia sin autorización está prohibida en virtud de la >>> legislación vigente. Si ha recibido este mensaje por error, le rogamos que >>> nos lo comunique inmediatamente por esta misma vía y proceda a su >>> destrucción. >>> >>> CONFIDENTIALITY WARNING. This message is intended exclusively for its >>> addressee and may contain information that is CONFIDENTIAL and protected by >>> professional privilege. If you are not the intended recipient you are >>> hereby notified that any dissemination, copy or disclosure of this >>> communication is strictly prohibited by law. If this message has been >>> received in error, please immediately notify us via e-mail and delete it. >>> >> -- AVISO DE CONFIDENCIALIDAD. Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o CONFIDENCIAL. Si no es Vd. el destinatario indicado, queda notificado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. CONFIDENTIALITY WARNING. This message is intended exclusively for its addressee and may contain information that is CONFIDENTIAL and protected by professional privilege. If you are not the intended recipient you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received in error, please immediately notify us via e-mail and delete it.
