I run OMV6 and after I shutdown my system to install a new HDD, docker is no longer working. I have just updated all packages to the latest version without resolve although this fault should not be due to some previous update taking effect upon booting up again as the server was restarted 2 days ago without the new drive and no update was done in between.
This is the error in journalctl:
Code
Subject: A start job for unit containerd.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit containerd.service has begun execution.
░░
░░ The job identifier is 37153.
May 06 18:32:16 mothership containerd[19211]: panic: the type must be a pointer to register as an untyped conversion
May 06 18:32:16 mothership containerd[19211]: goroutine 1 [running]:
May 06 18:32:16 mothership containerd[19211]: k8s.io/apimachinery/pkg/util/runtime.Must(...)
May 06 18:32:16 mothership containerd[19211]: /go/src/github.com/containerd/containerd/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:171
May 06 18:32:16 mothership containerd[19211]: k8s.io/apiserver/pkg/audit.init.1()
May 06 18:32:16 mothership containerd[19211]: /go/src/github.com/containerd/containerd/vendor/k8s.io/apiserver/pkg/audit/scheme.go:37 +0x1e5
May 06 18:32:16 mothership systemd[1]: containerd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit containerd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 2.
May 06 18:32:16 mothership systemd[1]: containerd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit containerd.service has entered the 'failed' state with result 'exit-code'.
May 06 18:32:16 mothership systemd[1]: Failed to start containerd container runtime.
░░ Subject: A start job for unit containerd.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit containerd.service has finished with a failure.
░░
░░ The job identifier is 37153 and the job result is failed.systemctl status docker.service:
Code
● 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 Mon 2024-05-06 18:36:35 CEST; 9min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Process: 20534 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 20534 (code=exited, status=1/FAILURE)
May 06 18:35:35 mothership systemd[1]: Starting Docker Application Container Engine...
May 06 18:35:35 mothership dockerd[20534]: time="2024-05-06T18:35:35.963358950+02:00" level=info msg="Starting up"
May 06 18:35:35 mothership dockerd[20534]: time="2024-05-06T18:35:35.963404958+02:00" level=warning msg="Running experimental build"
May 06 18:35:35 mothership dockerd[20534]: time="2024-05-06T18:35:35.964169989+02:00" level=info msg="detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf"
May 06 18:36:25 mothership dockerd[20534]: time="2024-05-06T18:36:25.823999220+02:00" level=info msg="Processing signal 'terminated'"
May 06 18:36:35 mothership dockerd[20534]: failed to start daemon: failed to dial "/run/containerd/containerd.sock": failed to dial "/run/containerd/containerd.sock": context deadline exceeded
May 06 18:36:35 mothership systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
May 06 18:36:35 mothership systemd[1]: docker.service: Failed with result 'exit-code'.
May 06 18:36:35 mothership systemd[1]: Stopped Docker Application Container Engine.Any idea what I can try?
