Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
So in order to confirm my theory I now tried the deploy_cluster.yml ansible playbook with the following variable in my ansible inventory file set: openshift_use_crio=True When I do that the the sym link from /var/lib/docker to /var/lib/containers/docker gets created properly. The problem now is that I am using CentOS Atomic Host and it looks like there is no CRI-O available on Atomic Host... Maybe someone here has an idea how I can get CRI-O running on CentOS Atomic Host??? or is it not possible and one is stuck with Docker? ‐‐‐ Original Message ‐‐‐ On Friday, January 25, 2019 8:25 PM, Mateus Caruccio wrote: > I'm not sure that is the case. This file is included from [1]. MAybe someone > from redhat team could drop some wisdom. > > [1] > https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/container_runtime/tasks/package_docker.yml#L174 > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > Em sex, 25 de jan de 2019 às 16:48, mabi escreveu: > >> There are no symlinks and /var/lib/docker still exists. Looking at the >> following playbook: >> >> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml >> >> I can see that the symlink only gets created when using CRI-O with OpenShift >> (openshift_use_crio). As I am not using CRI-O but Docker it looks like the >> symlink will never get created correctly... >> >> Is this maybe an issue to be reported? >> >> ‐‐‐ Original Message ‐‐‐ >> On Friday, January 25, 2019 7:02 PM, Mateus Caruccio >> wrote: >> >>> There should be a symlink /var/lib/docker pointing to >>> /var/lib/containers/docker. >>> >>> -- >>> Mateus Caruccio / Master of Puppets >>> GetupCloud.com >>> We make the infrastructure invisible >>> Gartner Cool Vendor 2017 >>> >>> Em sex, 25 de jan de 2019 às 11:43, mabi escreveu: >>> I changed the /etc/sysconfig/docker-storage-setup to use /var/lib/containers instead of /var/lib/docker in the CONTAINER_ROOT_LV_MOUNT_PATH variable and the OpenShift ansible prerequisites.yml playbook now worked fine. So I now I went on to the next step of the installation which is to run the OpenShift ansible deploy_cluster.yml playbook and this one fails because it tries do pull a docker image and store it into /var/lib/docker as you can see from the output below in this mail... Here is the command I am running: atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts --set PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 And here the failing output from ansible: TASK [openshift_node : Copy node container image to ostree storage] Friday 25 January 2019 13:18:08 + (0:00:31.595) 0:03:12.069 FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (1 retries left). fatal: [inst4.mydomain.org]: FAILED! => {"attempts": 3, "changed": false, "cmd": ["atomic", "pull", "--storage=ostree", "docker:docker.io/openshift/origin-node:v3.11"], "delta": "0:00:08.381259", "end": "2019-01-25 14:19:01.462409", "msg": "non-zero return code", "rc": 1, "start": "2019-01-25 14:18:53.081150", "stderr": "time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing source docker-daemon:openshift/origin-node:v3.11: Error loading image from docker engine: Error response from daemon: write /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: no space left on device\" ", "stderr_lines": ["time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing source docker-daemon:openshift/origin-node:v3.11: Error loading image from docker engine: Error response from daemon: write /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: no space left on device\" "], "stdout": "", "stdout_lines": []} ‐‐‐ Original Message ‐‐‐ On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio wrote: > oops, didn't noticed that message. I guess you could simply m
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
I'm not sure that is the case. This file is included from [1]. MAybe someone from redhat team could drop some wisdom. [1] https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/container_runtime/tasks/package_docker.yml#L174 -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em sex, 25 de jan de 2019 às 16:48, mabi escreveu: > There are no symlinks and /var/lib/docker still exists. Looking at the > following playbook: > > > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml > > I can see that the symlink only gets created when using CRI-O with > OpenShift (openshift_use_crio). As I am not using CRI-O but Docker it > looks like the symlink will never get created correctly... > > > > Is this maybe an issue to be reported? > > ‐‐‐ Original Message ‐‐‐ > On Friday, January 25, 2019 7:02 PM, Mateus Caruccio < > mateus.caruc...@getupcloud.com> wrote: > > There should be a symlink /var/lib/docker pointing to > /var/lib/containers/docker. > > > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > > Em sex, 25 de jan de 2019 às 11:43, mabi escreveu: > >> I changed the /etc/sysconfig/docker-storage-setup to use >> /var/lib/containers instead of /var/lib/docker in the >> CONTAINER_ROOT_LV_MOUNT_PATH variable and the OpenShift ansible >> prerequisites.yml playbook now worked fine. >> >> So I now I went on to the next step of the installation which is to run >> the OpenShift ansible deploy_cluster.yml playbook and this one fails >> because it tries do pull a docker image and store it into /var/lib/docker >> as you can see from the output below in this mail... >> >> Here is the command I am running: >> >> atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts >> --set >> PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml >> --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 >> >> And here the failing output from ansible: >> >> TASK [openshift_node : Copy node container image to ostree storage] >> >> Friday 25 January 2019 13:18:08 + (0:00:31.595) 0:03:12.069 >> >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (1 retries >> left). >> fatal: [inst4.mydomain.org]: FAILED! => {"attempts": 3, "changed": >> false, "cmd": ["atomic", "pull", "--storage=ostree", "docker: >> docker.io/openshift/origin-node:v3.11"], "delta": "0:00:08.381259", >> "end": "2019-01-25 14:19:01.462409", "msg": "non-zero return code", "rc": >> 1, "start": "2019-01-25 14:18:53.081150", "stderr": >> "time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing >> source docker-daemon:openshift/origin-node:v3.11: Error loading image from >> docker engine: Error response from daemon: write >> /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: >> no space left on device\" ", "stderr_lines": >> ["time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing >> source docker-daemon:openshift/origin-node:v3.11: Error loading image from >> docker engine: Error response from daemon: write >> /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: >> no space left on device\" "], "stdout": "", "stdout_lines": []} >> >> >> >> >> ‐‐‐ Original Message ‐‐‐ >> On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio < >> mateus.caruc...@getupcloud.com> wrote: >> >> oops, didn't noticed that message. I guess you could simply mount overlay >> over /var/lib/containers >> >> -- >> Mateus Caruccio / Master of Puppets >> GetupCloud.com >> We make the infrastructure invisible >> Gartner Cool Vendor 2017 >> >> >> Em qui, 24 de jan de 2019 às 18:10, mabi escreveu: >> >>> Thank you Mateus for the hint regarding the new storage dir. >>> >>> However I am not sure it it will help with the installation because you >>> mention that I should mount my overlay2 LVM partition in >>> docker_alt_storage_path, which is actually /var/lib/containers/docker >>> >>> Now the "no space left on device" error message I got during the >>> installation was for the directory: /var/lib/containers/atomic/... The >>> /var/lib/containers/atomic directory is still located on the small 3 GB >>> root partition.
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
There are no symlinks and /var/lib/docker still exists. Looking at the following playbook: https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml I can see that the symlink only gets created when using CRI-O with OpenShift (openshift_use_crio). As I am not using CRI-O but Docker it looks like the symlink will never get created correctly... Is this maybe an issue to be reported? ‐‐‐ Original Message ‐‐‐ On Friday, January 25, 2019 7:02 PM, Mateus Caruccio wrote: > There should be a symlink /var/lib/docker pointing to > /var/lib/containers/docker. > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > Em sex, 25 de jan de 2019 às 11:43, mabi escreveu: > >> I changed the /etc/sysconfig/docker-storage-setup to use /var/lib/containers >> instead of /var/lib/docker in the CONTAINER_ROOT_LV_MOUNT_PATH variable and >> the OpenShift ansible prerequisites.yml playbook now worked fine. >> >> So I now I went on to the next step of the installation which is to run the >> OpenShift ansible deploy_cluster.yml playbook and this one fails because it >> tries do pull a docker image and store it into /var/lib/docker as you can >> see from the output below in this mail... >> >> Here is the command I am running: >> >> atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts >> --set >> PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml >> --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 >> >> And here the failing output from ansible: >> >> TASK [openshift_node : Copy node container image to ostree storage] >> >> Friday 25 January 2019 13:18:08 + (0:00:31.595) 0:03:12.069 >> >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (3 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (2 retries >> left). >> FAILED - RETRYING: Copy node container image to ostree storage (1 retries >> left). >> fatal: [inst4.mydomain.org]: FAILED! => {"attempts": 3, "changed": false, >> "cmd": ["atomic", "pull", "--storage=ostree", >> "docker:docker.io/openshift/origin-node:v3.11"], "delta": "0:00:08.381259", >> "end": "2019-01-25 14:19:01.462409", "msg": "non-zero return code", "rc": 1, >> "start": "2019-01-25 14:18:53.081150", "stderr": >> "time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing >> source docker-daemon:openshift/origin-node:v3.11: Error loading image from >> docker engine: Error response from daemon: write >> /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: >> no space left on device\" ", "stderr_lines": >> ["time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing >> source docker-daemon:openshift/origin-node:v3.11: Error loading image from >> docker engine: Error response from daemon: write >> /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: >> no space left on device\" "], "stdout": "", "stdout_lines": []} >> >> ‐‐‐ Original Message ‐‐‐ >> On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio >> wrote: >> >>> oops, didn't noticed that message. I guess you could simply mount overlay >>> over /var/lib/containers >>> >>> -- >>> Mateus Caruccio / Master of Puppets >>> GetupCloud.com >>> We make the infrastructure invisible >>> Gartner Cool Vendor 2017 >>> >>> Em qui, 24 de jan de 2019 às 18:10, mabi escreveu: >>> Thank you Mateus for the hint regarding the new storage dir. However I am not sure it it will help with the installation because you mention that I should mount my overlay2 LVM partition in docker_alt_storage_path, which is actually /var/lib/containers/docker Now the "no space left on device" error message I got during the installation was for the directory: /var/lib/containers/atomic/... The /var/lib/containers/atomic directory is still located on the small 3 GB root partition. Or am I missing something? ‐‐‐ Original Message ‐‐‐ On Thursday, January 24, 2019 7:44 PM, Mateus Caruccio wrote: > Since the introduction of cri-o, the docker storage dir was moved to > /var/lib/containers/docker and /var/lib/docker is a symlink to it. You > can see it in action in [1] and [2]. > > Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` > > [1] > https
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
There should be a symlink /var/lib/docker pointing to /var/lib/containers/docker. -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em sex, 25 de jan de 2019 às 11:43, mabi escreveu: > I changed the /etc/sysconfig/docker-storage-setup to use > /var/lib/containers instead of /var/lib/docker in the > CONTAINER_ROOT_LV_MOUNT_PATH variable and the OpenShift ansible > prerequisites.yml playbook now worked fine. > > So I now I went on to the next step of the installation which is to run > the OpenShift ansible deploy_cluster.yml playbook and this one fails > because it tries do pull a docker image and store it into /var/lib/docker > as you can see from the output below in this mail... > > Here is the command I am running: > > atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts > --set > PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml > --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 > > And here the failing output from ansible: > > TASK [openshift_node : Copy node container image to ostree storage] > > Friday 25 January 2019 13:18:08 + (0:00:31.595) 0:03:12.069 > > FAILED - RETRYING: Copy node container image to ostree storage (3 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (3 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (3 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (2 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (2 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (2 retries > left). > FAILED - RETRYING: Copy node container image to ostree storage (1 retries > left). > fatal: [inst4.mydomain.org]: FAILED! => {"attempts": 3, "changed": false, > "cmd": ["atomic", "pull", "--storage=ostree", "docker: > docker.io/openshift/origin-node:v3.11"], "delta": "0:00:08.381259", > "end": "2019-01-25 14:19:01.462409", "msg": "non-zero return code", "rc": > 1, "start": "2019-01-25 14:18:53.081150", "stderr": > "time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing > source docker-daemon:openshift/origin-node:v3.11: Error loading image from > docker engine: Error response from daemon: write > /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: > no space left on device\" ", "stderr_lines": > ["time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing > source docker-daemon:openshift/origin-node:v3.11: Error loading image from > docker engine: Error response from daemon: write > /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: > no space left on device\" "], "stdout": "", "stdout_lines": []} > > > > > ‐‐‐ Original Message ‐‐‐ > On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio < > mateus.caruc...@getupcloud.com> wrote: > > oops, didn't noticed that message. I guess you could simply mount overlay > over /var/lib/containers > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > > Em qui, 24 de jan de 2019 às 18:10, mabi escreveu: > >> Thank you Mateus for the hint regarding the new storage dir. >> >> However I am not sure it it will help with the installation because you >> mention that I should mount my overlay2 LVM partition in >> docker_alt_storage_path, which is actually /var/lib/containers/docker >> >> Now the "no space left on device" error message I got during the >> installation was for the directory: /var/lib/containers/atomic/... The >> /var/lib/containers/atomic directory is still located on the small 3 GB >> root partition. >> >> Or am I missing something? >> >> >> >> ‐‐‐ Original Message ‐‐‐ >> On Thursday, January 24, 2019 7:44 PM, Mateus Caruccio < >> mateus.caruc...@getupcloud.com> wrote: >> >> Since the introduction of cri-o, the docker storage dir was moved to >> /var/lib/containers/docker and /var/lib/docker is a symlink to it. You can >> see it in action in [1] and [2]. >> >> Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` >> >> [1] >> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml#L2 >> [2] >> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/setup_docker_symlink.yml >> [3] >> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47 >> >> -- >> Mateus Caruccio / Master of Puppets >> GetupCloud.com >> We make the infrastructure invisible >> Gartner Cool Vendor 2017 >> >> >> Em qui, 24 de jan de 2019 às 15:52, mabi escreveu: >> >>> Hi, >>> >>> I am trying to install OKD version 3.11 on CentOS 7 Atomic Host using >>> the offic
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
I changed the /etc/sysconfig/docker-storage-setup to use /var/lib/containers instead of /var/lib/docker in the CONTAINER_ROOT_LV_MOUNT_PATH variable and the OpenShift ansible prerequisites.yml playbook now worked fine. So I now I went on to the next step of the installation which is to run the OpenShift ansible deploy_cluster.yml playbook and this one fails because it tries do pull a docker image and store it into /var/lib/docker as you can see from the output below in this mail... Here is the command I am running: atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts --set PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/deploy_cluster.yml --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 And here the failing output from ansible: TASK [openshift_node : Copy node container image to ostree storage] Friday 25 January 2019 13:18:08 + (0:00:31.595) 0:03:12.069 FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (3 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (2 retries left). FAILED - RETRYING: Copy node container image to ostree storage (1 retries left). fatal: [inst4.mydomain.org]: FAILED! => {"attempts": 3, "changed": false, "cmd": ["atomic", "pull", "--storage=ostree", "docker:docker.io/openshift/origin-node:v3.11"], "delta": "0:00:08.381259", "end": "2019-01-25 14:19:01.462409", "msg": "non-zero return code", "rc": 1, "start": "2019-01-25 14:18:53.081150", "stderr": "time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing source docker-daemon:openshift/origin-node:v3.11: Error loading image from docker engine: Error response from daemon: write /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: no space left on device\" ", "stderr_lines": ["time=\"2019-01-25T14:19:01+01:00\" level=fatal msg=\"Error initializing source docker-daemon:openshift/origin-node:v3.11: Error loading image from docker engine: Error response from daemon: write /var/lib/docker/tmp/docker-export-196848125/d43adf9eb4cc67bbc8d08f6922ff9fdfcbb1830a8b586f24dfc4afa335a1c51b/layer.tar: no space left on device\" "], "stdout": "", "stdout_lines": []} ‐‐‐ Original Message ‐‐‐ On Thursday, January 24, 2019 9:40 PM, Mateus Caruccio wrote: > oops, didn't noticed that message. I guess you could simply mount overlay > over /var/lib/containers > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > Em qui, 24 de jan de 2019 às 18:10, mabi escreveu: > >> Thank you Mateus for the hint regarding the new storage dir. >> >> However I am not sure it it will help with the installation because you >> mention that I should mount my overlay2 LVM partition in >> docker_alt_storage_path, which is actually /var/lib/containers/docker >> >> Now the "no space left on device" error message I got during the >> installation was for the directory: /var/lib/containers/atomic/... The >> /var/lib/containers/atomic directory is still located on the small 3 GB root >> partition. >> >> Or am I missing something? >> >> ‐‐‐ Original Message ‐‐‐ >> On Thursday, January 24, 2019 7:44 PM, Mateus Caruccio >> wrote: >> >>> Since the introduction of cri-o, the docker storage dir was moved to >>> /var/lib/containers/docker and /var/lib/docker is a symlink to it. You can >>> see it in action in [1] and [2]. >>> >>> Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` >>> >>> [1] >>> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml#L2 >>> [2] >>> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/setup_docker_symlink.yml >>> [3] >>> https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47 >>> >>> -- >>> Mateus Caruccio / Master of Puppets >>> GetupCloud.com >>> We make the infrastructure invisible >>> Gartner Cool Vendor 2017 >>> >>> Em qui, 24 de jan de 2019 às 15:52, mabi escreveu: >>> Hi, I am trying to install OKD version 3.11 on CentOS 7 Atomic Host using the official documentation here: https://docs.okd.io/3.11/install/running_install.html#running-the-advanced-installation-containerized So after running the following command: atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts --set PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/prerequisites.yml --set OPTS="-v
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
oops, didn't noticed that message. I guess you could simply mount overlay over /var/lib/containers -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em qui, 24 de jan de 2019 às 18:10, mabi escreveu: > Thank you Mateus for the hint regarding the new storage dir. > > However I am not sure it it will help with the installation because you > mention that I should mount my overlay2 LVM partition in > docker_alt_storage_path, which is actually /var/lib/containers/docker > > Now the "no space left on device" error message I got during the > installation was for the directory: /var/lib/containers/atomic/... The > /var/lib/containers/atomic directory is still located on the small 3 GB > root partition. > > Or am I missing something? > > > > ‐‐‐ Original Message ‐‐‐ > On Thursday, January 24, 2019 7:44 PM, Mateus Caruccio < > mateus.caruc...@getupcloud.com> wrote: > > Since the introduction of cri-o, the docker storage dir was moved to > /var/lib/containers/docker and /var/lib/docker is a symlink to it. You can > see it in action in [1] and [2]. > > Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` > > [1] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml#L2 > [2] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/setup_docker_symlink.yml > [3] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47 > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > > Em qui, 24 de jan de 2019 às 15:52, mabi escreveu: > >> Hi, >> >> I am trying to install OKD version 3.11 on CentOS 7 Atomic Host using the >> official documentation here: >> >> >> https://docs.okd.io/3.11/install/running_install.html#running-the-advanced-installation-containerized >> >> So after running the following command: >> >> atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts >> --set >> PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/prerequisites.yml >> --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 >> >> I get the following output/error: >> >> Getting image source signatures >> Copying blob >> sha256:a02a4930cb5d36f3290eb84f4bfa30668ef2e9fe3a1fb73ec015fc58b9958b17 >> 71.68 MB / 71.68 MB >> [==] 6s >> Copying blob >> sha256:16ffbd784f7768f3ebfc1697df136659c6c3481754263b6f852317c5f948b860 >> 9.57 MB / 9.57 MB >> [] 0s >> Copying blob >> sha256:df4469e6f51747d98306dd4d60d23b0ef6386e0ae55eafc2473745ce0d12f6f5 >> 271 B / 271 B >> [] 0s >> Copying blob >> sha256:36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7 >> 201.01 MB / 201.01 MB >> [===] 18s >> Copying config >> sha256:184868402205ab5533ce71b76c1cc1edf9d9d98227c2de845f90b83a67f0a52c >> 4.80 KB / 4.80 KB >> [] 0s >> Writing manifest to image destination >> Storing signatures >> FATA[0118] Error committing the finished image: mkdir >> /var/lib/containers/atomic/.CjIXZk/docker.io_2Fopenshift_2Forigin-ansible_3Av3.11/36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7/root/usr/share/ansible/openshift-ansible/roles/nuage_node/vars: >> no space left on device >> >> As you see it looks like the directory /var/lib/containers is used but it >> should actually be using /var/lib/docker, that is where I have configured >> my LVM thin layer volume for Docker storage. >> >> How can I change that directory? or should I configure my docker storage >> to use /var/lib/containers instead? >> >> For setting up my docker storage using the Overlay2 driver I followed the >> following guide: >> >> >> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#using_the_overlay_graph_driver >> >> Thanks for any hints. >> >> Regards, >> Mabi >> >> ___ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> > > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
Thank you Mateus for the hint regarding the new storage dir. However I am not sure it it will help with the installation because you mention that I should mount my overlay2 LVM partition in docker_alt_storage_path, which is actually /var/lib/containers/docker Now the "no space left on device" error message I got during the installation was for the directory: /var/lib/containers/atomic/... The /var/lib/containers/atomic directory is still located on the small 3 GB root partition. Or am I missing something? ‐‐‐ Original Message ‐‐‐ On Thursday, January 24, 2019 7:44 PM, Mateus Caruccio wrote: > Since the introduction of cri-o, the docker storage dir was moved to > /var/lib/containers/docker and /var/lib/docker is a symlink to it. You can > see it in action in [1] and [2]. > > Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` > > [1] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml#L2 > [2] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/setup_docker_symlink.yml > [3] > https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47 > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > Em qui, 24 de jan de 2019 às 15:52, mabi escreveu: > >> Hi, >> >> I am trying to install OKD version 3.11 on CentOS 7 Atomic Host using the >> official documentation here: >> >> https://docs.okd.io/3.11/install/running_install.html#running-the-advanced-installation-containerized >> >> So after running the following command: >> >> atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts >> --set >> PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/prerequisites.yml >> --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 >> >> I get the following output/error: >> >> Getting image source signatures >> Copying blob >> sha256:a02a4930cb5d36f3290eb84f4bfa30668ef2e9fe3a1fb73ec015fc58b9958b17 >> 71.68 MB / 71.68 MB >> [==] 6s >> Copying blob >> sha256:16ffbd784f7768f3ebfc1697df136659c6c3481754263b6f852317c5f948b860 >> 9.57 MB / 9.57 MB >> [] 0s >> Copying blob >> sha256:df4469e6f51747d98306dd4d60d23b0ef6386e0ae55eafc2473745ce0d12f6f5 >> 271 B / 271 B >> [] 0s >> Copying blob >> sha256:36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7 >> 201.01 MB / 201.01 MB [===] >> 18s >> Copying config >> sha256:184868402205ab5533ce71b76c1cc1edf9d9d98227c2de845f90b83a67f0a52c >> 4.80 KB / 4.80 KB >> [] 0s >> Writing manifest to image destination >> Storing signatures >> FATA[0118] Error committing the finished image: mkdir >> /var/lib/containers/atomic/.CjIXZk/docker.io_2Fopenshift_2Forigin-ansible_3Av3.11/36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7/root/usr/share/ansible/openshift-ansible/roles/nuage_node/vars: >> no space left on device >> >> As you see it looks like the directory /var/lib/containers is used but it >> should actually be using /var/lib/docker, that is where I have configured my >> LVM thin layer volume for Docker storage. >> >> How can I change that directory? or should I configure my docker storage to >> use /var/lib/containers instead? >> >> For setting up my docker storage using the Overlay2 driver I followed the >> following guide: >> >> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#using_the_overlay_graph_driver >> >> Thanks for any hints. >> >> Regards, >> Mabi >> >> ___ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
Re: atomic install wants to use /var/lib/containers instead of /var/lib/docker for storage
Since the introduction of cri-o, the docker storage dir was moved to /var/lib/containers/docker and /var/lib/docker is a symlink to it. You can see it in action in [1] and [2]. Make sure to mount your overlay2 partition at [3]`docker_alt_storage_path` [1] https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/post.yml#L2 [2] https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/tasks/common/setup_docker_symlink.yml [3] https://github.com/openshift/openshift-ansible/blob/master/roles/container_runtime/defaults/main.yml#L47 -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em qui, 24 de jan de 2019 às 15:52, mabi escreveu: > Hi, > > I am trying to install OKD version 3.11 on CentOS 7 Atomic Host using the > official documentation here: > > > https://docs.okd.io/3.11/install/running_install.html#running-the-advanced-installation-containerized > > So after running the following command: > > atomic install --system --storage=ostree --set INVENTORY_FILE=/root/hosts > --set > PLAYBOOK_FILE=/usr/share/ansible/openshift-ansible/playbooks/prerequisites.yml > --set OPTS="-v" docker.io/openshift/origin-ansible:v3.11 > > I get the following output/error: > > Getting image source signatures > Copying blob > sha256:a02a4930cb5d36f3290eb84f4bfa30668ef2e9fe3a1fb73ec015fc58b9958b17 > 71.68 MB / 71.68 MB > [==] 6s > Copying blob > sha256:16ffbd784f7768f3ebfc1697df136659c6c3481754263b6f852317c5f948b860 > 9.57 MB / 9.57 MB > [] 0s > Copying blob > sha256:df4469e6f51747d98306dd4d60d23b0ef6386e0ae55eafc2473745ce0d12f6f5 > 271 B / 271 B > [] 0s > Copying blob > sha256:36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7 > 201.01 MB / 201.01 MB > [===] 18s > Copying config > sha256:184868402205ab5533ce71b76c1cc1edf9d9d98227c2de845f90b83a67f0a52c > 4.80 KB / 4.80 KB > [] 0s > Writing manifest to image destination > Storing signatures > FATA[0118] Error committing the finished image: mkdir > /var/lib/containers/atomic/.CjIXZk/docker.io_2Fopenshift_2Forigin-ansible_3Av3.11/36fd26a639ac48c560feb36254ec2f3de38e915b93d5f6bf7749abd675f7f0c7/root/usr/share/ansible/openshift-ansible/roles/nuage_node/vars: > no space left on device > > As you see it looks like the directory /var/lib/containers is used but it > should actually be using /var/lib/docker, that is where I have configured > my LVM thin layer volume for Docker storage. > > How can I change that directory? or should I configure my docker storage > to use /var/lib/containers instead? > > For setting up my docker storage using the Overlay2 driver I followed the > following guide: > > > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/managing_containers/managing_storage_with_docker_formatted_containers#using_the_overlay_graph_driver > > Thanks for any hints. > > Regards, > Mabi > > ___ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > ___ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users