docker: Have to restart the containers to "mount" the hdd's. Is there a way to avoid this (delay or something?)

Hi,
there is a problem with the containers i use (sabnzbd and jellyfin).

When i reboot the server, the containers do not "find" the hdd's and write to the system (16gb sd-card).

When i stop and restart the containers, everything works fine.

Do i have to use a delay or something similar to have a successful mount after a reboot?

BTW:
The sdcard is almost full (!), because i accidentally downloaded some stuff to the system.
But I cannot find the downloads to delete them.
There are downloads-folder but they are empty.
How can i find or delete the downloads which seems to be stored in the containers?

regards
moddy

Thank you macom.

docker:
I installed docker again and now i have to wait and watch.
Hope this was the solution.

Nice How-to!
So I found out that the folder /var/lib/docker/overlay2 is the large one.

So I ran

docker image prune --all

It has reclaimed my disk space (16 GB) by around 7 GB, which was being used up by files under /var/lib/docker/overlay2.

Thanks again for your help

The space-problem is solved, but the docker-issue is still there.

I installed docker "again".

Docker storage :: /var/lib/docker
Agent port:: 8000
Web port:: 9000
Yacht port:: 8001
arch   :: arm64
option :: docker
state  :: install
extras :: 5.6.2
DNS OK.
Create override file ...
Reload systemd daemon ...
Skipping docker restart.
Done.

But after a reboot, there containers still fail to mount the hdd's.

Is there another way?

Zitat von KM0201

Is your system completely up to date?

Yes, this is always the first thing i do when sth. does not work as expected.

Zitat

There's no information about the system but judging from the output of docker this is a RPi, so how are the drives powered? are both drives connected to the USB3 ports? Simple test would be to be shutdown and move one of the drives to the a USB2 port, does it solve the problem.

It is an odroid hc4 (the "toaster").
It is an sbc but with 2 SATA-ports.

https://www.hardkernel.com/shop/odroid-hc4/

Zitat von macom

What is the output of

cat /etc/systemd/system/docker.service.d/waitAllMounts.conf?

Hmmm, there is no such or similar file...

Zitat von geaves

Having established what the hardware is, surely the question would be how was OMV installed

OS is a Debian GNU/Linux 10 (buster).

Linux 5.11.0-odroid-arm64
#1 SMP PREEMPT Debian 5.11.18-202108050550~buster (2021-08-04)
aarch64 GNU/Linux

OMV was installed by this script i Think.
https://github.com/OpenMediaVa…-Developers/installScript

It is a few months ago and went very well, so i do not really remember.
The common disadvantage of stable running systems.

Zitat von macom

Should have been created during the re-installation of docker (if the filesystems were mounted during re-installation)

RE: Is your docker also corrupt after a reboot? (OMV5, Pi4) This might fix it!

https://github.com/OpenMediaVault-Plugin-Developers/openmediavault-omvextrasorg/blob/master/usr/sbin/omv-installdocker#L317

I do not really understand.