Portainer, Yacht, and Docker-CE will not install after update

Nexceda · Jan 20th 2023

So, I just ran the update for the latest OMV and when I rebooted I had a whole host of errors that needed resolving, Including logs clogging up my rootfs so that I could log on. And a mostly root owned FS. The issue now is that a portainer install was not found although docker was. And when I went to reinstall docker/portainer i got the error that docker-ce and portainer could not install.

Error was:

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) Drop-In: /etc/systemd/system/docker.service.d └─waitAllMounts.conf Active: activating (auto-restart) (Result: exit-code) since Fri 2023-01-20 03:42:17 PST; 12ms ago
TriggeredBy: ● docker.socket Docs: https://docs.docker.com Process: 69607 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=2) Main PID: 69607 (code=exited, status=2) CPU: 1.337s
dpkg: error processing package docker-ce (--configure): installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing: docker-ce

Please help, I had so many docker images before that I ran my nas setup with.

Nexceda · Jan 21st 2023

Additionally, I've tried force installing, clearing the apt cache. I have no idea what happened to it. I would be more than happy to just reinstall omv via the iso if I knew how to copy all my docker configs

macom · Jan 21st 2023

Quote from Nexceda

See "systemctl status docker.service" and "journalctl -xe" for details.

Post the output of each of the following commands in a code box. You create a code box with the </> icon in the menu on top of a new post.

Code

systemctl start docker.service
systemctl status socker.service
journalctl -xe

Nexceda · Jan 21st 2023

I just decided to go ahead and reinstall from the ISO and back up my docker volumes. Thanks anyways though.

buchi66 · Feb 19th 2023

Hallo

habe am Wochende auf 2 verschiedenen PC omv6 installiert ,danach omv extras .Aus OMV extras installierte ich dan Docker und anschließend Portainer .Der Status von Portainer wird als created angezeigt ,aber Portainer lässt sich nicht im Browser öffnen .

Hat jemand vlielleicht eine Lösung für mich ?

Besten Dank

Wolf2000 · Feb 19th 2023

Hi

Post

RE: docker not working since omv-upgrade

*** This is for amd64 and i386 only ***
Here is the solution to disable apparmor on the system and it worked on my test system (not harmful since apparmor package is not installed):
(Code, 4 lines)

Taken from: https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor

If you have portainer and/or yacht installed, they will most likely need to be remove and reinstalled. You will not lose settings if this is done with omv-extras.

ryecoaaron

Feb 2nd 2023

Blabla · Feb 25th 2023

Not OP,but I'm having the same issue:

Quote from macom
Post the output of each of the following commands in a code box. You create a code box with the </> icon in the menu on top of a new post.
Code
systemctl start docker.service
systemctl status socker.service
journalctl -xe

Code

root@delibird:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-02-25 12:25:21 CET; 2min 36s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 1063 (dockerd)
      Tasks: 19
     Memory: 131.3M
        CPU: 1.313s
     CGroup: /system.slice/docker.service
             └─1063 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.771405567+01:00" level=error msg="stream copy error: reading from a closed fifo"
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.771832024+01:00" level=error msg="stream copy error: reading from a closed fifo"
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.915571715+01:00" level=error msg="cf29256072a3a3b8ef1272967f0ccd7bc089a583619181930f6a74ce2fd7>
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.915640885+01:00" level=error msg="failed to start container" container=cf29256072a3a3b8ef12729>
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.915898828+01:00" level=info msg="Loading containers: done."
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.960764325+01:00" level=info msg="Docker daemon" commit=bc3805a graphdriver=overlay2 version=23>
Feb 25 12:25:20 delibird dockerd[1063]: time="2023-02-25T12:25:20.962013587+01:00" level=info msg="Daemon has completed initialization"
Feb 25 12:25:21 delibird dockerd[1063]: time="2023-02-25T12:25:21.049431332+01:00" level=info msg="[core] [Server #7] Server created" module=grpc
Feb 25 12:25:21 delibird systemd[1]: Started Docker Application Container Engine.
Feb 25 12:25:21 delibird dockerd[1063]: time="2023-02-25T12:25:21.057197033+01:00" level=info msg="API listen on /run/docker.sock"

root@delibird:~# journalctl -xe
░░
░░ A start job for unit openmediavault-beep-up.service has finished successfully.
░░
░░ The job identifier is 133.
Feb 25 12:25:23 delibird systemd[1]: Startup finished in 18.775s (kernel) + 10.176s (userspace) = 28.952s.
░░ Subject: System start-up is now complete
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ All system services necessary queued for starting at boot have been
░░ started. Note that this does not mean that the machine is now idle as services
░░ might still be busy with completing start-up.
░░
░░ Kernel start-up required 18775485 microseconds.
░░
░░ Initial RAM disk start-up required INITRD_USEC microseconds.
░░
░░ Userspace start-up required 10176671 microseconds.
Feb 25 12:25:45 delibird systemd[1]: systemd-fsckd.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit systemd-fsckd.service has successfully entered the 'dead' state.
Feb 25 12:25:46 delibird monit[1018]: 'delibird' Monit 5.27.2 started
Feb 25 12:25:46 delibird monit[1018]: Queued event file: unable to read event size -- end of file
Feb 25 12:25:48 delibird chronyd[970]: Selected source 193.204.114.232 (ntp1.inrim.it)
Feb 25 12:25:48 delibird chronyd[970]: System clock wrong by 1.148254 seconds
Feb 25 12:25:49 delibird chronyd[970]: System clock was stepped by 1.148254 seconds
Feb 25 12:26:02 delibird CRON[2450]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 25 12:26:02 delibird CRON[2451]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
Feb 25 12:26:02 delibird wakealarm[2452]: INFO - No alarm set previously.
Feb 25 12:26:02 delibird wakealarm[2452]: INFO - Next alarm: 2023-02-25 18:00:00
Feb 25 12:26:02 delibird wakealarm[2452]: INFO - Wakealarm set to: 2023-02-25 18:00:00
Feb 25 12:26:02 delibird CRON[2450]: pam_unix(cron:session): session closed for user root
Feb 25 12:27:01 delibird CRON[2461]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 25 12:27:01 delibird CRON[2462]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
Feb 25 12:27:01 delibird wakealarm[2463]: INFO - Current alarm: 2023-02-25 18:00:00
Feb 25 12:27:01 delibird wakealarm[2463]: INFO - Next alarm: 2023-02-25 18:00:00
Feb 25 12:27:01 delibird wakealarm[2463]: WARNING - No alarm to be set.
Feb 25 12:27:01 delibird CRON[2461]: pam_unix(cron:session): session closed for user root
Feb 25 12:27:11 delibird openmediavault-webgui[2464]: Authorized login from 192.168.1.2 [username=admin, user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv>
Feb 25 12:27:38 delibird sshd[2980]: Accepted password for root from 192.168.1.2 port 59880 ssh2
Feb 25 12:27:38 delibird sshd[2980]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Feb 25 12:27:38 delibird su[2989]: (to root) root on pts/0
Feb 25 12:27:38 delibird su[2989]: pam_unix(su:session): session opened for user root(uid=0) by root(uid=0)
Feb 25 12:27:38 delibird sshd[2984]: Accepted password for root from 192.168.1.2 port 59881 ssh2
Feb 25 12:27:38 delibird sshd[2984]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Feb 25 12:28:01 delibird CRON[3448]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 25 12:28:01 delibird CRON[3449]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
Feb 25 12:28:01 delibird wakealarm[3450]: INFO - Current alarm: 2023-02-25 18:00:00
Feb 25 12:28:01 delibird wakealarm[3450]: INFO - Next alarm: 2023-02-25 18:00:00
Feb 25 12:28:01 delibird wakealarm[3450]: WARNING - No alarm to be set.
Feb 25 12:28:01 delibird CRON[3448]: pam_unix(cron:session): session closed for user root
lines 2218-2271/2271 (END)

Display More

macom · Feb 25th 2023

Not the same issue. Your docker seems to be running as expected. What is your issue?

Blabla · Feb 25th 2023

Portainer is not starting, I tried to install it again but it won't update and start.

The other docker, like plex, won't start either.

Should I open a new topic since it's different?

macom · Feb 25th 2023

Did you check if the grub fix helps?

If you did and it does not work, then yes, I think it would be better to start a new thread.

Blabla · Feb 25th 2023

Solved for me too!

Portainer, Yacht, and Docker-CE will not install after update

geaves Jan 20th 2023

Participate now!

Tags