docker not starting after OMV update

MarcS · 19. April 2021

I had Docker running nicely with Portainer and several live containers (Nginx, Nextcloud, Pihole).

After a recent OMV update I cannot get Docker up again. I am posting the output below. Maybe someone can help interpret this.

Journalctl -xe output:

Code

A stop job for unit docker.service has finished.
--
-- The job identifier is 87250 and the job result is done.
Apr 19 21:56:41 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 21:56:41 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Apr 19 21:56:41 pi3 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit docker.service has finished with a failure.
--
-- The job identifier is 87250 and the job result is failed.
Apr 19 21:56:41 pi3 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.

Alles anzeigen

and the output of systemctl status...

Code

root@pi3:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 22:01:13 BST; 16ms ago
Docs: https://docs.docker.com
Process: 11586 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=
Main PID: 11586 (code=exited, status=1/FAILURE)


Apr 19 22:01:13 pi3 systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 19 22:01:13 pi3 systemd[1]: Stopped Docker Application Container Engine.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 19 22:01:13 pi3 systemd[1]: Failed to start Docker Application Container Engine.
root@pi3:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 22:01:13 BST; 50s ago
Docs: https://docs.docker.com
Process: 11586 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=
Main PID: 11586 (code=exited, status=1/FAILURE)


Apr 19 22:01:13 pi3 systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 19 22:01:13 pi3 systemd[1]: Stopped Docker Application Container Engine.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Start request repeated too quickly.
Apr 19 22:01:13 pi3 systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 19 22:01:13 pi3 systemd[1]: Failed to start Docker Application Container Engine.

Alles anzeigen

macom · 20. April 2021

The docker service file has a restart=always policy. It helped me sometimes to trouble shoot an issue with a service to disabel that policy.

Usually I edit the service file directly, but a better method is to write an override file. So lets try

systemctl edit docker.service

paste

Code

[Service]
Restart=
Restart=no

then

systemctl status docker.service

To undo the change (remove the override file)

systemctl revert docker.service

pre5ton · 21. April 2021

I'm experiencing the same problem. Everything working great in OMV and Portainer until updating OMV on Sunday 4/18. Now docker will not start or restart. I have tried uninstalling docker and receive errors upon trying to reinstall.

Below is my systemctl status.

Code

docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-04-20 21:29:23 MST; 6min ago
Docs: https://docs.docker.com
Process: 1661 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 1661 (code=exited, status=1/FAILURE)


Apr 20 21:29:23 openmediavault.local systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 20 21:29:23 openmediavault.local systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 20 21:29:23 openmediavault.local systemd[1]: Stopped Docker Application Container Engine.
Apr 20 21:29:23 openmediavault.local systemd[1]: docker.service: Start request repeated too quickly.
Apr 20 21:29:23 openmediavault.local systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 20 21:29:23 openmediavault.local systemd[1]: Failed to start Docker Application Container Engine.

Alles anzeigen

MarcS · 21. April 2021

Seems to be the same problem. I dont even want to re-install docker as I have so many containers up and running which took me weeks to configure. I fear they might all be gone if I re-install Docker.

Is there any one that can help on this Docker issue. Seems to be cause be a recent OMV update.

many thanks

Agricola · 24. April 2021

Your containers will not be affected by a docker reinstall. With your existing setup do you have your Docker storage path to somewhere on /srv?

MarcS · 25. April 2021

yes my docker storage path points to a disk that is now (surprisingly) empty. Something must have happened during the OMV upgrade...one disk is completely empty and that was the disk where my Docker path is pointing to.

MarcS · 25. April 2021

So I solved the problem. The issue was some confusion with the mount-points.

I have several LUKS encrypted disks which I decrypt after booting via a script but apparently that now doesn't work anymore after the OMV update. I have to manually decrypt the disks each by hand in the OMV GUI.

After doing that, the Docker path is visible again and docker works.

Agricola · 25. April 2021

That encryption will trip you up every time. Glad you found your docker files.

cubemin · 26. April 2021

This should help: Auto-unlock LUKS volumes on boot

MarcS · 26. April 2021

thanks for the link but this defeats this process seems to automatically unlock all drives after reboot.

That would defeat the whole purpose of drive encryption.

In my solution, there is a manual step, i.e. running of a shell script as root.

Jetzt mitmachen!