moby: Ubuntu 16.04 clean install of docker-engine fails to initialize network bridge

On a clean installation of 1.11.2 on Ubuntu 16.04 xenial docker daemon fails to start reporting: "=“Error starting daemon: Error initializing network controller: Error creating default "bridge" network: failed to parse pool request for address space "LocalDefault" pool "" subpool "": could not find an available predefined network”

when called via sudo service docker start as listed in the installation page. When calling via sudo docker daemon at first I get the error Error starting daemon: error initializing graphdriver: “/var/lib/docker” contains several valid graphdrivers: aufs, overlay; Please cleanup or explicitly choose storage driver (-s <DRIVER>)

But if I, as suggested by the error message, call sudo docker daemon -s overlay or -s aufs I again receive the error message from above.

I did read through the issues with the same error from earlier versions of docker and attempted the workarounds found there, namely sudo rm -rf /var/lib/docker/network which does not resolve the issue. The other solution my research brought up was to use ifconfig docker0 down, and then restart the bridge, but in this scenario there is no docker0 adapter to disable when I attempt to start the daemon, so I didn’t continue down that path.

I considered posting this in #18113, however it is closed due to being reported as fixed in version 1.10.0, so I’ve created a new one as it would appear to still be an issue, let me know if that was incorrect.


BUG REPORT INFORMATION

Docker Version

Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 22:00:43 2016
 OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Output of docker info:

Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Additional environment details (AWS, VirtualBox, physical, etc.): Physical computer running Ubuntu 16.04 output of uname -a:

Linux quinn-Inspiron-5547 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the issue:

  1. Run: sudo service docker start -> receive error
  2. Run: systemctl status docker.service

Describe the results you received: Full log from systemctl status docker.service

● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2016-07-17 15:27:01 EDT; 10min ago
     Docs: https://docs.docker.com
  Process: 30547 ExecStart=/usr/bin/docker daemon -s overlay -H fd:// (code=exited, status=1/FAILURE)
 Main PID: 30547 (code=exited, status=1/FAILURE)

Jul 17 15:27:00 quinn-Inspiron-5547 systemd[1]: Starting Docker Application Container Engine...
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.876634901-04:00" level=info msg="previous instance of containerd still alive (14264)"
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.940600196-04:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.946582731-04:00" level=info msg="Firewalld running: false"
Jul 17 15:27:01 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:01.024951094-04:00" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to parse pool request for address space \"LocalDefault\" pool \"\" subpool \"\": could not find an available predefined network"
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: Failed to start Docker Application Container Engine.
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Unit entered failed state.
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Failed with result 'exit-code'.

relevant output of journalctl -xe:

Jul 17 15:27:00 quinn-Inspiron-5547 sudo[30445]:    quinn : TTY=pts/5 ; PWD=/home/quinn ; USER=root ; COMMAND=/usr/sbin/service docker start
Jul 17 15:27:00 quinn-Inspiron-5547 sudo[30445]: pam_unix(sudo:session): session opened for user root by quinn(uid=0)
Jul 17 15:27:00 quinn-Inspiron-5547 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.
Jul 17 15:27:00 quinn-Inspiron-5547 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.
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.876634901-04:00" level=info msg="previous instance of containerd still alive (14264)"
Jul 17 15:27:00 quinn-Inspiron-5547 audit[30557]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=30557 comm="apparmor_parser"
Jul 17 15:27:00 quinn-Inspiron-5547 kernel: audit: type=1400 audit(1468783620.901:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="docker-default" pid=30557 comm="apparmor_parser"
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.940600196-04:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Jul 17 15:27:00 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:00.946582731-04:00" level=info msg="Firewalld running: false"
Jul 17 15:27:01 quinn-Inspiron-5547 docker[30547]: time="2016-07-17T15:27:01.024951094-04:00" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: failed to parse pool request for address space \"LocalDefault\" pool \"\" subpool \"\": could not find an available predefined network"
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Jul 17 15:27:01 quinn-Inspiron-5547 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.
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Unit entered failed state.
Jul 17 15:27:01 quinn-Inspiron-5547 systemd[1]: docker.service: Failed with result 'exit-code'.

Describe the results you expected:

No error code and a running docker daemon preferably.

Additional information you deem important (e.g. issue happens only occasionally): Occurs consistently despite multiple reboots, attempts etc.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

@quinnkjones

I just faced the same issue. In my case, it was my VPN who was causing trouble. As soon as I disconnected, the installation worked. Then I connected the VPN again and run the docker hello-world command and it works. Not sure if that helps you, but it is worth try it.

So apparently this happens intermittently as it is now happening again!
Here is the output of route:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.4.128.1      0.0.0.0         UG    600    0        0 wlp2s0
10.0.0.0        10.4.128.1      255.0.0.0       UG    600    0        0 wlp2s0
10.4.128.0      *               255.255.240.0   U     600    0        0 wlp2s0
157.182.0.0     10.4.128.1      255.255.0.0     UG    600    0        0 wlp2s0
157.182.94.70   10.4.128.1      255.255.255.255 UGH   600    0        0 wlp2s0
172.16.0.0      10.4.128.1      255.240.0.0     UG    600    0        0 wlp2s0
192.168.0.0     10.4.128.1      255.255.0.0     UG    600    0        0 wlp2s0

My guess now is that the main difference between the set of times when I could run docker and the set of times I couldn’t is that I can run docker in my apartment (or more accurately when I’m on my apartments very simple network), but when I’m at work (rather on a university buildings network) the routes are different enough to cause the error. Is the problem the A class netmask on 10.0.0.0? or the ambitious default gateway?

@quinnkjones Please check https://github.com/docker/libnetwork/issues/779 Check if there is any route in your sytem which would mask all the predefined address pools from which docker picks a subnet for the default bridge network (docker0). Usually vpn routes would do so.