![]() ![]() On it, we create the volume group like this: vgcreate dockervg /dev/sdb We then format /dev/sdb (but we don’t create a partition). Our docker-storage-setup will look like this (taken from this RedHat post section 2.6) : ~ # > more /etc/sysconfig/docker-storage-setup STORAGE_DRIVER= overlay2 DEVS= /dev/sdb WIPE_SIGNATURES=true CONTAINER_ROOT_LV_NAME= dockerlv CONTAINER_ROOT_LV_SIZE=100%FREE CONTAINER_ROOT_LV_MOUNT_PATH=/var/lib/docker VG= dockervg On our master, we have three files, the /etc/sysconfig/docker /etc/sysconfig/docker-storage /etc/sysconfig/docker-storage-setupĪs as setup, we want to have our external disk /dev/sdb as a docker volume. Maybe it’s a good moment to stop and have a look to the docker configuration. Here the documentation of the docker-storage-setup. How can we change that? It turned out that our docker system is controlled by two daemon, the docker and the docker-storage-setup. It turned out that it’s a feature, not a limitation, of the new overlay driver. ln -s /var/lib/docker /data_networkĪfter the restart, unfortunately, we still see that overlay and shm are the same size. We stop the docker daemon and softlink the /var/lib/docker to our network storage. ![]() We are going to tell our master to use a secondary device disk as docker file system. We get that from docker info (only relevant information displayed here) ~ # > docker info | grep Storage Storage Driver: overlay2 We need to find out what docker Storage Driver we use on the host. But that’s not the point, the point is that we want to configure where those docker partitions go. Why is it so? Is it because of the host disk size? It may be. It is clear the partition overlay is full. var/lib/ docker/overlay2/-hash1-/merged shm 64M 0 64M 0%īut if I stop the docker and remove the image, the overlay and shm partitions disappear. In my case, with the container running, I see my partitions like: # > df -h Filesystem Size Used Avail Use% Mounted on tmpfs 16G 68M 16G 1% /dev/shm /dev/sdc2 99G 93G 670M 100% / /dev/sdc1 477M 176M 273M 40% /boot tmpfs 3.1G 52K 3.1G 1% /run/user/1036 overlay 99G 93G 670M 100% It depends on your OS and your docker version. How’s the docker disk space managed? There’s not a single answer. Error Summary - Disk Requirements: At least 159MB more space needed on the / filesystem. Everything seems to be fine, but I need to install a lot of packages, resulting on this error. First I login as root user: docker exec -it -user root centosvnc /bin/bash Let’s say I have my docker centosvnc and I want to install R on it, like when I first encounter this issue. One of my favourite images now is consol/centos-xfce-vnc since it allows me to give an user a VNC connection to the docker. I tend to add software to my dockers once I have them running.
0 Comments
Leave a Reply. |