I had been running Docker for about a week. I am using the Docker CE packages from the Docker repo. Docker version 20.10.13, build a224086. This morning there were some CentOS updates that required a reboot. I was running Portainer and used it to stop 2 containers before I rebooted.
After the reboot, Docker won’t start. I don’t have much to go on as to what the reason is but maybe someone may have an idea.
I have uninstalled and re-installed Docker. I have removed the directories in /var/lib. Stil won’t start.
This is the output of systemctl status docker:
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-03-23 12:56:13 EDT; 1h 11min ago
Docs: https://docs.docker.com
Process: 207433 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 207433 (code=exited, status=1/FAILURE)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
The .sock file exists.
That’s not much help for me maybe someone has an idea. I can post whatever file you may need.
I edited your post to fix your inserted systemctl output. Please, use the codeblock button (</>) when you want to share code or any command line output so the it will be readable keeping the indentations.
I don’t see any error message that would inidicate otherwise. Have you tried running journalctl to see the logs?
[root@ts130 ~]# journalctl -xe -u docker
-- Automatic restarting of the unit docker.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Mar 23 15:12:23 xxxxxxxxxxxxxxxx.com systemd[1]: Stopped Docker Application Container Engine.
-- Subject: Unit docker.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit docker.service has finished shutting down.
Mar 23 15:12:23xxxxxxxxxxxxx.com systemd[1]: docker.service: Start request repeated too quickly.
Mar 23 15:12:23 xxxxxxxxxxxx.com systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Mar 23 15:12:23 xxxxxxxxxxxxx.com systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit docker.service has failed.
--
-- The result is failed.
Then try journalctl without specifying the service:
journalctl -xe
Maybe an other dependency failed like containerd. The other thing that you could try is running dockerd without systemd to see the logs in the foreground
I get nothing when I run journalctl -xe
containerd is running
Output from command line:
[root@ts130 ~]# /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
INFO[2022-03-23T16:49:16.917594165-04:00] Starting up
failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd
Yes, running journalctl -xe there is nothing there.
Running systemctl status docker.socket:
[root@ts130 ~]# systemctl status docker.socket
● docker.socket - Docker Socket for the API
Loaded: loaded (/usr/lib/systemd/system/docker.socket; disabled; vendor preset: disabled)
Active: failed (Result: service-start-limit-hit) since Wed 2022-03-23 16:48:37 EDT; 4h 33min ago
Listen: /var/run/docker.sock (Stream)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Running /usr/bin/dockered:
[root@ts130 ~]# /usr/bin/dockerd
INFO[2022-03-23T21:22:49.700094864-04:00] Starting up
INFO[2022-03-23T21:22:49.702236122-04:00] parsed scheme: "unix" module=grpc
INFO[2022-03-23T21:22:49.702268327-04:00] scheme "unix" not registered, fallback to default scheme module=grpc
INFO[2022-03-23T21:22:49.702292270-04:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2022-03-23T21:22:49.702302252-04:00] ClientConn switching balancer to "pick_first" module=grpc
INFO[2022-03-23T21:22:49.707847133-04:00] parsed scheme: "unix" module=grpc
INFO[2022-03-23T21:22:49.707883784-04:00] scheme "unix" not registered, fallback to default scheme module=grpc
INFO[2022-03-23T21:22:49.707907440-04:00] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock <nil> 0 <nil>}] <nil> <nil>} module=grpc
INFO[2022-03-23T21:22:49.707917675-04:00] ClientConn switching balancer to "pick_first" module=grpc
WARN[2022-03-23T21:22:49.851175387-04:00] Your kernel does not support cgroup blkio weight
WARN[2022-03-23T21:22:49.851206213-04:00] Your kernel does not support cgroup blkio weight_device
INFO[2022-03-23T21:22:49.851334395-04:00] Loading containers: start.
INFO[2022-03-23T21:22:49.904451654-04:00] Firewalld: docker zone already exists, returning
INFO[2022-03-23T21:22:50.507845204-04:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address
failed to start daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: ZONE_CONFLICT: 'docker0' already bound to a zone
type or paste code here
It was a kernel update I got today. Maybe that’s the problem. i think CentOS keeps the last 3 to 5 kernels available in case there is a problem. Think I should try to boot to the last kernel?