OMV6 - Docker's containers don't start after boot

Quote from Spirare

Hi,

OMV-EXTRA Docker 5:20.10.21~3-0~debian-bullseye

Fresh install...

None of my containers (including Portainer) start automatically after booting or rebooting.

Restart policies is set at "unless stop" for all containers.

OMV-EXTRA GUI report Docker to be up & running after rebooting.

In order to get all containers to start automatically, I need to 'restart' Docker via the OMV_EXTRA GUI.

Am I missing something here?

Any hints on how to solve this ?

Thanks

Display More

Did you upgraded from OMV5 or is it a fresh OMV6 install?

How did you install docker?

Quote from Spirare

OMV6 Fresh install...both Armbian Bullseye (Debian 11) and thereafter OMV6.

OMV6 installed with armbian-config script.

You're running on an Odroid or something?

On OMV6 fresh installs, the delay to wait for the drives to be mounted is already pre-configured so, your issue shouldn't happen.

You can try to, after restarting docker and the containers running properly, to press install again on OMVextras-->>Docker to see if it corrects itself.

Quote from Spirare

Ok, I just tried to re-install docker from OMVextra and rebooted...no change... the same problem

Post the output of:
cat /etc/fstab

omv-showkey mntent

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

Quote from Spirare

Just a thought...is there a way for me to increase the delay on my system for testing purpose?

There was a way on OMV5, but with OMV6, it shouln't be required because of how OMV installs docker and takes care of the dependency of the mounted drives prior to launch the docker/containers

I'm having this problem too. I've moved my Docker data off the root and to a disk (/srv/dev-disk-by-by-uuid-....) and my containers never come up on boot, even though they are set to restart: unless-stopped.

My OMV started at v5. I would guess the problem is that Docker is starting before the disk is mounted.

Quote from Soma

Post the output of:
cat /etc/fstab

omv-showkey mntent

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

I have no /etc/systemd/system/docker.service.d.

fstab says

UUID=9865a0b7-94e4-469a-8102-02611e455672 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/acc49cfe-4343-414f-8583-5575550dfac6        /srv/dev-disk-by-uuid-acc49cfe-4343-414f-8583-5575550dfac6    ext4    defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl    0 2
# <<< [openmediavault]

and omv-showkey says

$ sudo omv-showkey mntent
            <mntent>
                <uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
                <fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
                <dir>/xxx/yyy/zzz</dir>
                <type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
                <opts></opts>
                <freq>0</freq>
                <passno>0|1|2</passno>
                <hidden>0|1</hidden>
            </mntent>
      <mntent>
        <uuid>c5f393d7-e253-49c7-8290-7f7b82c2dd3b</uuid>
        <fsname>/dev/disk/by-uuid/acc49cfe-4343-414f-8583-5575550dfac6</fsname>
        <dir>/srv/dev-disk-by-uuid-acc49cfe-4343-414f-8583-5575550dfac6</dir>
        <type>ext4</type>
        <opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
        <freq>0</freq>
        <passno>2</passno>
        <hidden>0</hidden>
        <comment></comment>
        <usagewarnthreshold>85</usagewarnthreshold>
      </mntent>

Quote from hmoff

My OMV started at v5. I would guess the problem is that Docker is starting before the disk is mounted.

But did you upgraded to OMV6?

If you are already running OMV6, and on the omv-extras->docker GUI page, and you have the proper docker root path setted, just click install again and it will create the needed file.

Quote from Soma

If you are already running OMV6, and on the omv-extras->docker GUI page, and you have the proper docker root path setted, just click install again and it will create the needed file.

Thanks! That created the file, and now my containers starts on boot.

I had to add another dependency also to fix this. I have /home encrypted with fscrypt, and needed docker to wait until my unlock service ran before starting docker else the containers that need /home still fail.

Quote from macom

Did you create an override file? Otherwise your changes might be lost after the next update.

Thanks for the reminder, I have now.