Description
All our hosts have configured routes for the following networks:
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
So the default networks that dockerd tries to use for the docker0 bridge are already in use. Therefore I specify a custom bip which docker should use instead.
Steps to reproduce the issue:
- Configure routes for the networks given in the description on a host
- Start
dockerd with a bip which isn't part of one of the networks
Describe the results you received:
Relevant part of the logs:
Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network
If I configure the docker0 bridge manually dockerd starts sucessfully.
Describe the results you expected:
dockerd shouldn't check for available networks if a custom bip is specified.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:04:27 2017
OS/Arch: linux/amd64
Server:
Version: 17.05.0-ce
API version: 1.29 (minimum version 1.12)
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:04:27 2017
OS/Arch: linux/amd64
Experimental: false
Output of docker info:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 17.05.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Kernel Version: 4.9.0-0.bpo.3-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.799GiB
Name: xxx
ID: NSV4:YWNW:67GF:7SQN:YUD6:2NSE:U6VH:KNQW:L45F:S5PM:ZQWW:4TSW
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Description
All our hosts have configured routes for the following networks:
So the default networks that
dockerdtries to use for thedocker0bridge are already in use. Therefore I specify a custombipwhich docker should use instead.Steps to reproduce the issue:
dockerdwith abipwhich isn't part of one of the networksDescribe the results you received:
Relevant part of the logs:
If I configure the
docker0bridge manuallydockerdstarts sucessfully.Describe the results you expected:
dockerdshouldn't check for available networks if a custombipis specified.Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version:Output of
docker info: