sysad.mn

A collection of notes, guides, musings through the lenses of a Linux systems administrator

A collection of notes, guides, musings through the lenses of a Linux systems administrator

  • LinkedIn
  • Instagram
  • GitHub
Written with ❤

Docker fails to start “no available network”

15 August, 2019 By gerald Leave a Comment

Docker fails to start, restarting Docker service results in the following message:

1
2
[root@node2 ~]# 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.

Let’s check the systemd journal

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
[root@node2 ~]# journalctl -xe
--
-- Unit docker.socket has begun starting up.
Jun 20 13:47:56 node2 systemd[1]: Listening on Docker Socket for the API.
-- Subject: Unit docker.socket has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.socket has finished starting up.
--
-- The start-up result is done.
Jun 20 13:47:56 node2 systemd[1]: Starting Docker Application Container Engine...
-- Subject: Unit docker.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has begun starting up.
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.285428164+10:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.285547137+10:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" modu
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.285738147+10:00" level=info msg="parsed scheme: \"unix\"" module=grpc
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.285757414+10:00" level=info msg="scheme \"unix\" not registered, fallback to default scheme" modu
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286100178+10:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/co
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286104123+10:00" level=info msg="ccResolverWrapper: sending new addresses to cc: [{unix:///run/co
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286131531+10:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286143280+10:00" level=info msg="ClientConn switching balancer to \"pick_first\"" module=grpc
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286211695+10:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc42080b340, CONNE
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286217823+10:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420180960, CONNE
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286389419+10:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc42080b340, READY
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.286429051+10:00" level=info msg="pickfirstBalancer: HandleSubConnStateChange: 0xc420180960, READY
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.296358319+10:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.299625850+10:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.300173431+10:00" level=info msg="Loading containers: start."
Jun 20 13:47:56 node2 dockerd[46925]: time="2019-06-20T13:47:56.362964965+10:00" level=info msg="stopping event stream following graceful shutdown" error="<nil>"
Jun 20 13:47:56 node2 dockerd[46925]: Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network
Jun 20 13:47:56 node2 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE
Jun 20 13:47:56 node2 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Jun 20 13:47:56 node2 systemd[1]: Unit docker.service entered failed state.
Jun 20 13:47:56 node2 systemd[1]: docker.service failed.
1
2
3
4
5
[root@node2 network-scripts]# pwd;cat route-eth1
/etc/sysconfig/network-scripts
10.0.0.0/8 via 10.20.91.254
192.168.0.0/16 via 10.20.91.254
172.16.0.0/12 via 10.20.91.254

Steps to resolve:

  • Delete offending route “192.168.0.0/16 via 10.20.91.254”
  • Clear out Docker network directory
1
[root@node2 ~]# rm -rf /var/lib/docker/network
  • Restart Docker service
1
[root@node2 ~]# systemctl restart docker

Share this:

  • LinkedIn
  • Facebook
  • Twitter
  • WhatsApp
  • Skype
  • Print

Related

Tagged With: docker, network

Leave a Reply Cancel reply