A strange issue happened without a clear cause and by the time I didn’t fully understand why/how the solution worked, documented here for revisit if necessary.
Note: Run docker command with sudo is not encouraged, add user to docker group is preferred.
Issue:
Docker daemon startup fails contineously, checking deamon status and journal:
Feb 2804:42:32 chengdolgob.c.googlers.com systemd[1]: docker.service: Scheduled restart job, restart counter is at 2. Feb 2804:42:32 chengdolgob.c.googlers.com systemd[1]: Stopped Docker Application Container Engine. Feb 2804:42:32 chengdolgob.c.googlers.com systemd[1]: docker.service: Start request repeated too quickly. Feb 2804:42:32 chengdolgob.c.googlers.com systemd[1]: docker.service: Failed with result 'exit-code'. Feb 2804:42:32 chengdolgob.c.googlers.com systemd[1]: Failed to start Docker Application Container Engine
First to adjust the docker daemon unit file to disabke restart by commenting out:
1 2 3
#TimeoutSec=0 #RestartSec=10 #Restart=always
Then run systemctl daemon-reload and restart docker daemon to see detailed error message:
1 2 3
... Feb2804:43:46chengdolgob.c.googlers.comdockerd[7890]:failed to start daemon: Error initializing network controller: list bridge addresses failed: PredefinedLocalScopeDefaultNetworks List: [192.168.11.0/24]:noavailabl ...
Check the network interface ip a s, there is no docker0 bridge.
Solution:
To fix it, create new docker network bridge, reference ticket:
1 2 3 4 5 6 7 8
# delete docker0 bridge sudo ip link delete docker0
# 192.168.9.1/24 is from docker daemon.json bip field sudo ip link add name docker0 type bridge sudo ip addr add dev docker0 192.168.9.1/24 # or default sudo ip addr add dev docker0 172.17.0.1/16
The inet IP is from /etc/docker/daemon.json bip field, for example: