Moving docker installation with new docker-compose

m4tt0 · 24. Juni 2023

Sure, I appreciate your efforts! I've just reverted everything to "docker" again as the tests didn't work either.

Here you go. Screenshots from docker-compose Settings and the current shared folders again...

chente · 24. Juni 2023

Zitat von m4tt0

Here you go. Screenshots from docker-compose Settings and the current shared folders again...

Well nothing, everything seems correct. We will have to wait for ryecoaaron . I tried.

ryecoaaron · 24. Juni 2023

I am pretty sure your packages need to be fixed not the docker path. What is the output of:

dpkg -l | grep -E "openmedia|docker"

sudo apt-get -f install

m4tt0 · 24. Juni 2023

Cheers ryecoaaron! Here you go...

Output of dpkg -l | grep -E "openmedia|docker":

Code

ii docker-buildx-plugin 0.10.5-1~debian.11~bullseye amd64 Docker Buildx cli plugin.
ii docker-ce 5:24.0.2-1~debian.11~bullseye amd64 Docker: the open-source application container engine
ii docker-ce-cli 5:24.0.2-1~debian.11~bullseye amd64 Docker CLI: the open-source application container engine
ii docker-compose-plugin 2.18.1-1~debian.11~bullseye amd64 Docker Compose (V2) plugin for the Docker CLI.
ii openmediavault 6.4.5-1 all openmediavault - The open network attached storage solution
ii openmediavault-backup 6.1 all backup plugin for OpenMediaVault.
ii openmediavault-clamav 6.0.4-1 all openmediavault ClamAV plugin
ii openmediavault-compose 6.8 all OpenMediaVault compose plugin
ii openmediavault-cputemp 6.1.3 all cpu temperature plugin for openmediavault
ii openmediavault-diskstats 6.0.3-1 all openmediavault disk monitoring plugin
ii openmediavault-fail2ban 6.0.3 all OpenMediaVault Fail2ban plugin
ii openmediavault-flashmemory 6.2 all folder2ram plugin for openmediavault
ii openmediavault-kernel 6.4.8 all kernel package
ii openmediavault-keyring 1.0.2-2 all GnuPG archive keys of the openmediavault archive
ii openmediavault-kvm 6.2.15 all kvm plugin for OpenMediaVault.
ii openmediavault-mergerfs 6.3.7 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 6.3.1 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-resetperms 6.0.3 all Reset Permissions
ii openmediavault-sharerootfs 6.0.2-1 all openmediavault share root filesystem plugin
ii openmediavault-snapraid 6.1 all snapraid plugin for OpenMediaVault.
ii openmediavault-symlinks 6.0.4 all OpenMediaVault symlinks plugin
ii python3-docker 4.1.0-1.2 all Python 3 wrapper to access docker.io's control socket

Alles anzeigen

And here is the output of sudo apt-get -f install:

Code

Reading package lists...
Building dependency tree...
Reading state information...0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

The latter is not surprising to me, as I guess omv-upgrade fixed the errors there already...

ryecoaaron · 25. Juni 2023

What about:

sudo journalctl -u docker

sudo cat /etc/docker/daemon.json

sudo ls -al $(docker info | grep "Docker Root Dir" | awk '{ print $4 }')

m4tt0 · 25. Juni 2023

The output of journalctl -u docker is attached as text file (had to zip it again).

Otherwise...

Code

root@myrs:~# cat /etc/docker/daemon.json
{
  "data-root": "/srv/dev-disk-by-uuid-5c8e8fc1-94ee-431e-b45e-7939d6339072/docker"
}
root@myrs:~# ls -al $(docker info | grep "Docker Root Dir" | awk '{ print $4 }')
total 60
drwx--s--- 12 root users  4096 Jun 24 21:03 .
drwxr-xr-x  6 root root   4096 Jun 24 21:23 ..
drwx--x--x  4 root root   4096 Jun 24 14:27 buildkit
drwx--x--- 13 root root   4096 Jun 24 14:59 containers
-rw-------  1 root root     36 Jun 24 14:27 engine-id
drwx------  3 root root   4096 Jun 24 14:27 image
drwxr-x---  3 root root   4096 Jun 24 14:27 network
drwx--x--- 98 root root  12288 Jun 24 21:03 overlay2
drwx------  4 root root   4096 Jun 24 14:27 plugins
drwx------  2 root root   4096 Jun 24 21:03 runtimes
drwx------  2 root root   4096 Jun 24 14:27 swarm
drwx------  2 root root   4096 Jun 24 21:03 tmp
drwx-----x  2 root root   4096 Jun 24 21:03 volumes

Alles anzeigen

ryecoaaron · 25. Juni 2023

Zitat von m4tt0

The output of journalctl -u docker is attached as text file (had to zip it again).

It still can't find the metadata.db file. If it was my machine, I would stop/down all containers, stop the docker service (sudo systemctl stop docker), and delete everything in the docker directory. Then start docker again.

m4tt0 · 25. Juni 2023

You have contributed so much to the OMV code, that my machine basically is your machine...

I'll definitely try that! Could you just do me one more favor? Could you let me know what permissions the docker directory should have before I install it again?

ryecoaaron · 25. Juni 2023

Zitat von m4tt0

Could you let me know what permissions the docker directory should have before I install it again?

Code

aaron@omv6dev:~$ stat /var/lib/docker
File: /var/lib/docker
Size: 4096      	Blocks: 8          IO Block: 4096   directory
Device: fc01h/64513d	Inode: 1444601     Links: 12
Access: (0710/drwx--x---)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-06-24 17:24:41.791315426 -0500
Modify: 2023-06-25 03:14:46.322411009 -0500
Change: 2023-06-25 03:14:46.322411009 -0500
Birth: 2023-05-24 16:04:17.088862873 -0500

m4tt0 · 25. Juni 2023

I've done what you suggested and corrected the permissions of the docker folder (from 755 to 710) on the way. Everything worked without issues, including the restart of the docker environment. I was able to check that the metadata.db in the docker/volumes folder exists. journalctl -u docker did not expose any further errors. It seems it works now...

Cheers, ryecoaaron!!! Many thanks for your help!

Moving docker installation with new docker-compose

m4tt0 25. Juni 2023

Jetzt mitmachen!

Tags