You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues before opening this one
Expected behavior
When initializing swarm it will create different interfaces (docker0, docker_gwbridge) starting with a default 172.17.0.0/16 network.
We already have a 172.17.0.0/16 network defined and our VMs have a static route to reach it:
ip route
172.17.0.0/16 via 10.3.33.1 dev ens192
Usually Swarm was "seeing" this route and initialized its interfaces with another network (for example 172.18.0.0/16)
Since some recent docker update (something after 20.10.13 and before or equal to 20.10.17) the behavior has changed and Swarm creates a conflicting configuration.
Actual behavior
Actually Swarm initialize its interfaces with 172.17.0.0/16 wheter or not a static route is already defined on the server.
ip route
default via 10.3.33.1 dev ens192
10.3.33.0/24 dev ens192 proto kernel scope link src 10.3.33.242
172.17.0.0/16 via 10.3.33.1 dev ens192 # DHCP sent static route
172.17.0.0/16 dev docker_gwbridge proto kernel scope link src 172.17.0.1 # Swarm create a conflicting route
192.168.13.0/24 dev docker0 proto kernel scope link src 192.168.13.1 linkdown
Steps to reproduce the behavior
With a fresh VM that already has a static route configured like this:
172.17.0.0/16 via 10.3.33.1 dev ens192
Install docker, it will create an interface that conflicts with the static route.
In fact it is not linked to Swarm only but the way Docker checks for available network range on the local machine before create a new network (docker bridge network for example).
Expected behavior
When initializing swarm it will create different interfaces (
docker0
,docker_gwbridge
) starting with a default 172.17.0.0/16 network.We already have a 172.17.0.0/16 network defined and our VMs have a static route to reach it:
Usually Swarm was "seeing" this route and initialized its interfaces with another network (for example 172.18.0.0/16)
Since some recent docker update (something after 20.10.13 and before or equal to 20.10.17) the behavior has changed and Swarm creates a conflicting configuration.
Actual behavior
Actually Swarm initialize its interfaces with 172.17.0.0/16 wheter or not a static route is already defined on the server.
Steps to reproduce the behavior
With a fresh VM that already has a static route configured like this:
172.17.0.0/16 via 10.3.33.1 dev ens192
Install docker, it will create an interface that conflicts with the static route.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
If it can change something, it has to be said that the route is given by the DHCP server.
The text was updated successfully, but these errors were encountered: