Portainer loosing image details on reboot.

cyber7 · 6. Oktober 2020

Good morning everyone

Every time I reboot my system, Portainer shows unknown images for my docker-containers. It is very random and I can not pin-point where the fault lays. If I then run "Duplicate/Edit" or "Recreate" with the latest image, the container seems OK, but will randomly happen all over again on reboot...

This then leaves me with a bunch of unused images showing the release as "<none>":

And after a reboot, it will randomly start again...

How can I stop this behavior?

kind regards

cyber7

cyber7 · 6. Oktober 2020

It seems the problem is resolved with the following:

systemctl list-unit-files | grep “.mount”

Then running:

systemctl edit docker.service

and then adding a wait-state for the disks to start with:

Code

[Unit]
Requires=xxx.mount
After=xxx.mount

in my case:

Code

[Unit]
Requires=srv-dev\x2ddisk\x2dby\x2dlabel\x2d13TB.mount
After=srv-dev\x2ddisk\x2dby\x2dlabel\x2d13TB.mount

Note the extra characters and the format...

my mount is: /srv/dev-disk-by-label-13TB

original at: https://github.com/openmediavault/openmediavault/issues/458

tinh_x7 · 7. November 2020

Hi,

I currently have 3 hdd data disks, and 2 parity hdds.

Do I need to add all the data disks in the ' docker.service' ?

Code

srv-b697b778\x2d5898\x2d4418\x2db651\x2d3a2345ae8b7e.mount     generated
srv-dev\x2ddisk\x2dby\x2dlabel\x2ddata1.mount                  generated
srv-dev\x2ddisk\x2dby\x2dlabel\x2ddata2.mount                  generated
srv-dev\x2ddisk\x2dby\x2dlabel\x2ddata3.mount                  generated
srv-dev\x2ddisk\x2dby\x2dlabel\x2dparity1.mount                generated
srv-dev\x2ddisk\x2dby\x2dlabel\x2dparity2.mount                generated

Portainer loosing image details on reboot.

Jetzt mitmachen!

Tags