I managed to figure it out. I had to choose another docker daemon data storage directory with /etc/docker/daemon.json
Now it works Thanks a lot though!
I managed to figure it out. I had to choose another docker daemon data storage directory with /etc/docker/daemon.json
Now it works Thanks a lot though!
I see, thank you. I will try to redo the system and then for the data drives use raid1 with luks and ext4 file system only. I cannot imagine why docker would even care if itself is only on the boot drive which is not luks encrypted.
Hi! Thanks for the reply! Why would there be timing issues on boot? The LUKS container will have to be manually decrypted before LVM and so on is even a thing? Since im not an expert, what would you suggest I should do? And also why would a /srv/ directory on my main SSD be removed as the error states?
Hi everyone, im having issues mounting a filesystem.
What I've done:
Now I was trying to mount it but when trying to apply the pending configuration changes, after a second or two this error pops up everytime. I even restarted the operating system (of course unlocked the LUKS container).
I can say that I found this UUID in the docker inspect command when I checked my running docker containers listed as:
Zitat"MergedDir": "/srv/dev-disk-by-uuid-ca1d42af-c7b9-4520-9e3a-865a09d5fffc/docker/overlay2/26433e97be9dc284702480812329bb2ae98d39e385e1a6a1ac88bc214c1f89c2/merged",
"UpperDir": "/srv/dev-disk-by-uuid-ca1d42af-c7b9-4520-9e3a-865a09d5fffc/docker/overlay2/26433e97be9dc284702480812329bb2ae98d39e385e1a6a1ac88bc214c1f89c2/diff",
"WorkDir": "/srv/dev-disk-by-uuid-ca1d42af-c7b9-4520-9e3a-865a09d5fffc/docker/overlay2/26433e97be9dc284702480812329bb2ae98d39e385e1a6a1ac88bc214c1f89c2/work"
However these are located on the system SSD which is not being used for any storage. Just a few docker containers and OMV run on this. I dont understand why this could be a problem.
Thanks in advance!