Docker daemon fails to start on upgraded system

I have two systems (laptop and workstation), both have been upgraded to opensuse 15.6. One of them runs docker just fine (workstation), the other fails to do so.

> sudo systemctl restart docker
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xeu docker.service" for details.
myusername@myhostname:~> sudo systemctl status docker.service
× docker.service - Docker Application Container Engine
     Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-06-27 14:34:31 EDT; 3min 20s ago
TriggeredBy: × docker.socket
       Docs: http://docs.docker.com
    Process: 11399 ExecStart=/usr/bin/dockerd --add-runtime oci=/usr/sbin/docker-runc $DOCKER_NETWORK_OPTIONS $DOCKER_OPTS >
   Main PID: 11399 (code=exited, status=1/FAILURE)
        CPU: 212ms

Jun 27 14:34:31 myhostname systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Jun 27 14:34:31 myhostname systemd[1]: docker.service: Start request repeated too quickly.
Jun 27 14:34:31 myhostname systemd[1]: docker.service: Failed with result 'exit-code'.
Jun 27 14:34:31 myhostname systemd[1]: Failed to start Docker Application Container Engine.

Not sure how to debug this - it worked fine (for at least 15.4 and 15.5) on the same system. After uninstalling and removing /var/lib/docker, I reinstalled:

Retrieving: docker-24.0.7_ce-150000.198.2.x86_64 (Main Repository)                                      (1/4),  25.5 MiB    
Retrieving: docker-24.0.7_ce-150000.198.2.x86_64.rpm ....................................................[done (22.7 MiB/s)]
Retrieving: docker-buildx-0.11.2-bp156.1.12.x86_64 (Main Repository)                                    (2/4),  11.6 MiB    
Retrieving: docker-buildx-0.11.2-bp156.1.12.x86_64.rpm ..................................................[done (21.4 MiB/s)]
Retrieving: docker-rootless-extras-24.0.7_ce-150000.198.2.noarch (Main Repository)                      (3/4), 117.9 KiB    
Retrieving: docker-rootless-extras-24.0.7_ce-150000.198.2.noarch.rpm .....................................[done (3.0 KiB/s)]
Retrieving: docker-bash-completion-24.0.7_ce-150000.198.2.noarch (Main Repository)                      (4/4), 129.9 KiB    
Retrieving: docker-bash-completion-24.0.7_ce-150000.198.2.noarch.rpm .....................................[done (3.0 KiB/s)]

where “Main Repository” maps to

http://download.opensuse.org/distribution/leap/15.6/repo/oss/

Any help is appreciated.

More info:

/usr/bin/dockerd --add-runtime oci=/usr/sbin/docker-runc $DOCKER_NETWORK_OPTIONS $DOCKER_OPTS

from https://documentation.suse.com/smart/systems-management/html/task-debug-failed-systemd-services/index.html (thank you!) yielded… This

INFO[0000] SUSE:secrets :: enabled                      
WARN[2024-06-27T14:50:02.479902848-04:00] failed to load plugin io.containerd.snapshotter.v1.devmapper  error="devmapper not configured"
WARN[2024-06-27T14:50:02.480254947-04:00] could not use snapshotter devmapper in metadata plugin  error="devmapper not configured"
WARN[2024-06-27T14:50:02.537974532-04:00] Running modprobe bridge br_netfilter failed with message: modprobe: ERROR: could not insert 'bridge': Key was rejected by service
modprobe: ERROR: could not insert 'br_netfilter': Key was rejected by service
insmod /lib/modules/6.4.0-150600.21-default/kernel/net/llc/llc.ko.zst 
insmod /lib/modules/6.4.0-150600.21-default/kernel/net/llc/llc.ko.zst 
, error: exit status 1 
WARN[2024-06-27T14:50:02.758211526-04:00] Could not load necessary modules for IPSEC rules: protocol not supported 
ERRO[2024-06-27T14:50:02.766246472-04:00] Failed to create bridge docker0 via netlink   error="operation not supported"
failed to start daemon: Error initializing network controller: error creating default "bridge" network: operation not supported

IPv6 is disabled on this computer’s wireless interface.

What is the output of journalctl -xe docker.service?

On a hunch, I rebooted, thinking I may not have done so. Turns out, I must have updated the system, as the current (post-reboot) kernel is 6.4.0-150600.23.7-default - not 6.4.0-150600.21-default.

Sorry for wasting time because not adhering to the diamond rule of “reboot first , then post”

To state the obvious: it now works…

No worries - glad to hear things are working! :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.