Docker is dead after update

igonixio · 8. Oktober 2022

Hello,

i become a message from OMV6 that a reboot is required. After the reboot is docker dead. What can i do??

Code

uname -r
5.15.60-1-pve

Code

Oct 08 18:06:47 openmediavault systemd[1]: Starting Docker Socket for the API.
-- Subject: A start job for unit docker.socket has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.socket has begun execution.
-- 
-- The job identifier is 2949.
Oct 08 18:06:47 openmediavault systemd[1]: Listening on Docker Socket for the API.
-- Subject: A start job for unit docker.socket has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.socket has finished successfully.
-- 
-- The job identifier is 2949.
Oct 08 18:06:47 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 18:06:47 openmediavault 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'.
Oct 08 18:06:47 openmediavault 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 2846 and the job result is failed.
Oct 08 18:06:47 openmediavault 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

Code

systemctl status docker
* 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: failed (Result: exit-code) since Sat 2022-10-08 18:06:09 CEST; 8min ago
TriggeredBy: * docker.socket
       Docs: https://docs.docker.com
    Process: 5408 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 5408 (code=exited, status=1/FAILURE)
        CPU: 44ms

Oct 08 18:06:09 openmediavault systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Oct 08 18:06:09 openmediavault systemd[1]: Stopped Docker Application Container Engine.
Oct 08 18:06:09 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 18:06:09 openmediavault systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 08 18:06:09 openmediavault systemd[1]: Failed to start Docker Application Container Engine.
Oct 08 18:06:47 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 18:06:47 openmediavault systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 08 18:06:47 openmediavault systemd[1]: Failed to start Docker Application Container Engine.

Alles anzeigen

Code

/etc/apt/sources.list.d/omvextras.list
deb https://openmediavault-plugin-developers.github.io/packages/debian shaitan main
deb [arch=amd64] https://download.docker.com/linux/debian bullseye stable

The docker folder is readable and writable. Uninstall and reinstall has not solved the problem. What can i do??

Many Thanks

macom · 8. Oktober 2022

Are all filesystem available or is one missing?

Try

systemctl start docker

igonixio · 8. Oktober 2022

Code

systemctl start docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.

Code

df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7.7G     0  7.7G   0% /dev
tmpfs           1.6G  2.6M  1.6G   1% /run
/dev/sdf2        43G  7.3G   34G  19% /
tmpfs           7.8G     0  7.8G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sdf1       511M  3.8M  508M   1% /boot/efi
tmpfs           7.8G     0  7.8G   0% /tmp
/dev/sdg1        30G   20G  8.4G  71% /srv/dev-disk-by-id-ata-TS32GSSD370_C810840231-part1
/dev/sda1        14T  3.9T  7.1T  36% /omv_daten/btrfs
tmpfs           1.6G     0  1.6G   0% /run/user/1002

Alles anzeigen

Filesystems all online, enough space is free

macom · 8. Oktober 2022

Code

journalctl -xe

igonixio · 8. Oktober 2022

Code

-- The job identifier is 1606 and the job result is failed.
Oct 08 18:46:27 openmediavault systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 08 18:46:27 openmediavault systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit docker.service has finished.
-- 
-- The job identifier is 1717 and the job result is done.
Oct 08 18:46:27 openmediavault systemd[1]: Starting Docker Application Container Engine...
-- Subject: A start job for unit docker.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.service has begun execution.
-- 
-- The job identifier is 1717.
Oct 08 18:46:27 openmediavault dockerd[2203]: unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character '"' after object key:value pair
Oct 08 18:46:27 openmediavault systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit docker.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Oct 08 18:46:27 openmediavault 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'.
Oct 08 18:46:27 openmediavault 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 1717 and the job result is failed.
Oct 08 18:46:29 openmediavault systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 08 18:46:29 openmediavault systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit docker.service has finished.
-- 
-- The job identifier is 1828 and the job result is done.
Oct 08 18:46:29 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 18:46:29 openmediavault 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'.
Oct 08 18:46:29 openmediavault 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 1828 and the job result is failed.
Oct 08 18:46:29 openmediavault 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

igonixio · 8. Oktober 2022

Code

Oct 08 18:46:27 openmediavault dockerd[2203]: unable to configure the Docker daemon with file /etc/docker/daemon.json: invalid character '"' after object key:value pair

This error i have solved, was not the solution.

macom · 8. Oktober 2022

Zitat von igonixio

This error i have solved, was not the solution.

Then again

systemctl restart docker

systemctl status docker

journalctl -xe

And post the complete output with the command, the output and the prompt.

igonixio · 8. Oktober 2022

Code

root@openmediavault:/# systemctl restart docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
root@openmediavault:/#

Code

root@openmediavault:/# systemctl status docker
* 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: failed (Result: exit-code) since Sat 2022-10-08 20:38:25 CEST; 18s ago
TriggeredBy: * docker.socket
       Docs: https://docs.docker.com
    Process: 4008 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 4008 (code=exited, status=1/FAILURE)
        CPU: 45ms

Oct 08 20:38:25 openmediavault systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Oct 08 20:38:25 openmediavault systemd[1]: Stopped Docker Application Container Engine.
Oct 08 20:38:25 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 20:38:25 openmediavault systemd[1]: docker.service: Failed with result 'exit-code'.
Oct 08 20:38:25 openmediavault systemd[1]: Failed to start Docker Application Container Engine.
root@openmediavault:/#

Alles anzeigen

Code

root@openmediavault:/# journalctl -xe
-- Support: https://www.debian.org/support
-- 
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Oct 08 20:40:05 openmediavault 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 5003 and the job result is failed.
Oct 08 20:40:07 openmediavault systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Oct 08 20:40:07 openmediavault systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit docker.service has finished.
-- 
-- The job identifier is 5115 and the job result is done.
Oct 08 20:40:07 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 20:40:07 openmediavault 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'.
Oct 08 20:40:07 openmediavault 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 5115 and the job result is failed.
Oct 08 20:40:07 openmediavault 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'.
Oct 08 20:40:24 openmediavault systemd[1]: Starting Docker Socket for the API.
-- Subject: A start job for unit docker.socket has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.socket has begun execution.
-- 
-- The job identifier is 5330.
Oct 08 20:40:24 openmediavault systemd[1]: Listening on Docker Socket for the API.
-- Subject: A start job for unit docker.socket has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit docker.socket has finished successfully.
-- 
-- The job identifier is 5330.
Oct 08 20:40:24 openmediavault systemd[1]: docker.service: Start request repeated too quickly.
Oct 08 20:40:24 openmediavault 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'.
Oct 08 20:40:24 openmediavault 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 5227 and the job result is failed.
Oct 08 20:40:24 openmediavault 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'.
lines 3827-3910/3910 (END)

Alles anzeigen

igonixio · 8. Oktober 2022

Docker works

I dont know why, but it works. All fine. Thank you for help

foreverlate88 · 5. Februar 2023

Zitat von igonixio

Docker works
I dont know why, but it works. All fine. Thank you for help

I have the same error, how did you fix it ?

macom · 5. Februar 2023

Have a look at this thread

Beitrag

RE: docker not working since omv-upgrade

Evidently something changed in the latest docker package that is making it think apparmor is configured. I would not install apparmor. I will look for a solution but I am working.

ryecoaaron

2. Februar 2023

Docker is dead after update

macom 5. Februar 2023

Jetzt mitmachen!