Docker Install Fails on fresh OMV5 install and OMV4 ->5 upgrade

gwaitsi · 15. Mai 2020

Getting the below error on my OMV4->5 upgrade, and exactly the same error on a fresh OMV5 VM install.

considering all i want is my plexserver back, OMV5 upgrade has been a disaster for me.

Code

Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-15 10:09:05 CEST; 20ms ago
Docs: https://docs.docker.com
Process: 27629 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 27629 (code=exited, status=1/FAILURE)


May 15 10:09:05 eapenas.eapenet.lan systemd[1]: Failed to start Docker Application Container Engine.
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1

Alles anzeigen

gwaitsi · 20. Mai 2020

still failing with latest 4.7.1 update.

i've given up on OMV5 (shame 4 was superb) moving to freenas.

Code

setting up docker-ce (5:19.03.9~3-0~debian-buster) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2020-05-20 23:12:40 CEST; 22ms ago
Docs: https://docs.docker.com
Process: 16658 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 16658 (code=exited, status=1/FAILURE)
dpkg: error processing package docker-ce (--configure):
installed docker-ce package post-installation script subprocess returned error exit status 1
Setting up libisccfg163:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u1) ...
Setting up libbind9-161:amd64 (1:9.11.5.P4+dfsg-5.1+deb10u1) ...

Alles anzeigen

ryecoaaron · 21. Mai 2020

Zitat von gwaitsi

i've given up on OMV5 (shame 4 was superb) moving to freenas.

Did you look at the output of journalctl -u docker? The docker package failing to start isn't even the fault of OMV. OMV 5 is every bit as good as OMV 4. Volker has mentioned many times that the 4 to 5 upgrade is not supported. If you are willing to move to FreeNAS, why not consider a fresh install of OMV 5 first??

gwaitsi · 22. Mai 2020

Zitat von ryecoaaron

Did you look at the output of journalctl -u docker? The docker package failing to start isn't even the fault of OMV. OMV 5 is every bit as good as OMV 4. Volker has mentioned many times that the 4 to 5 upgrade is not supported. If you are willing to move to FreeNAS, why not consider a fresh install of OMV 5 first??

i installed a fresh version in a virtual box and suffered exactly the same problems.

losing plex was a disappointment. i preferred the plugin over docker. that's why i installed and removed docker in OMV4.

when i did a virtual setup of freenas, the plugins went first time without issue.

don't get me wrong, you guys have done a fabulous job over the years. i've gone from OMV2 through to the OMV 5 and aside from one disaster with the an initial raid failure (which moved me to rsync backups) she has worked liked a charm.

Nefertiti · 22. Mai 2020

I must say I would agree with gwaitsi although I do not use plugin, but docker at this time is definitely not working as smooth as omv4. I keep struggling for over a week with version 5, and I see myself going back and forth between both systems.

One among some issues, having this problem where portainer disappearing and cannot be reinstalled, also volumes path not always working

I did not give up on OMV5 but hopefully with some subsequent update all those issues will be past history, but for now I think OMV 5 is not really ready yet for prime time .

.

gderf · 22. Mai 2020

I've had the opposite experience and I have been on OMV 5 since last November when I upgraded my OMV 4.x install.

I have fourteen docker containers running.

Everything just works.

ryecoaaron · 22. Mai 2020

Zitat von gwaitsi

when i did a virtual setup of freenas, the plugins went first time without issue.

IX has over 100 people who work on freenas for their job and they probably get direct support from plex. OMV has two people who work on things when they have time. It amazes me that you had the same problems installing docker in a fresh VM. I have done this hundreds of times now and haven't had this issue. I can't figure out what you are doing different.

Zitat von gwaitsi

don't get me wrong, you guys have done a fabulous job over the years. i've gone from OMV2 through to the OMV 5 and aside from one disaster with the an initial raid failure (which moved me to rsync backups) she has worked liked a charm.

Seems a little quick to jump ship to freenas then. That is a whole different world with a very different level of support.

Zitat von Nefertiti

docker at this time is definitely not working as smooth as omv4

My experience mirrors gderf's. No issues at all. I use it at work for many, many things as well. It is different but once you get it, it works very well.

Zitat von Nefertiti

One among some issues, having this problem where portainer disappearing and cannot be reinstalled, also volumes path not always working

Sounds like docker starting before you storage is ready. I added to the plugin to start docker after the local filesystems are done but some usb drives/remote mounts/mergerfs pool on top of filesystem on top luks have issues being mounted before docker starts. Restarting docker would probably fix it or adding the gross override to just wait 30secs for storage to be ready.

geaves · 22. Mai 2020

Zitat von gwaitsi

i installed a fresh version in a virtual box and suffered exactly the same problems.

I have OMV5 install in VB on my W10 workstation, trying out raid, zfs, mergerfs, snapraid, I've removed docker reinstalled it moved it's path installed and removed containers and it just works, any errors have been of my own making changing from one setup to another.

Nefertiti · 22. Mai 2020

Zitat von ryecoaaron

Sounds like docker starting before you storage is ready. I added to the plugin to start docker after the local filesystems are done but some usb drives/remote mounts/mergerfs pool on top of filesystem on top luks have issues being mounted before docker starts. Restarting docker would probably fix it or adding the gross override to just wait 30secs for storage to be ready.

I do not know if is related: I got 2 sd both with OMV5 and without changing anything in dockers ( relative paths) one of them make me land on a generic welcome page for Emby, Jellyfish, Airsonic and probably some other But I have not check them, the other OMV5 give me regular working library for those and I think I applied this mod for both Is your docker also corrupt after a reboot? (OMV5, Pi4) This might fix it!

magarity · 30. Mai 2020

Before you move to freenas make sure you go buy a Supermicro based system with ECC memory installed. I started with freenas and had a simple question about my ASUS motherboard based system and the answer was "go buy a Supermicro because we can't support all the other brands/models". Meanwhile OMV forums don't seem to care even if you're poking along on a Pi.

Jetzt mitmachen!