-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for specifying docker swarm subnet ranges #22
Labels
enhancement
New feature or request
Comments
When I "refresh" my VMs next, this will be a good time to do this, due to the fact that you can only change the subnet ranges during a |
per docs this is acheived by creating the docker network before running For example the order would be:
docker network create \
--subnet=10.200.0.0/16 \
--gateway 10.200.0.1 \
-o com.docker.network.bridge.enable_icc=false \
-o com.docker.network.bridge.name=docker_gwbridge \
-o com.docker.network.bridge.enable_ip_masquerade=true \
docker_gwbridge docker swarm init |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ran into an issue IP conflict recently that took me 2 weeks to debug 😨 ... Only to find out that docker swarm creates overlay networks starting with the private class A subnet range
10.0.0.0/8
and goes up from there sequentially, per swarm.Basically I was having issues with my pfSense OpenVPN connection that I set to subnet
10.0.0.0/24
. Everything worked, except I was unable to load web pages served from docker swarm lol. Usingdocker network inspect ingress
I found that swarm was setting the this network to10.0.0.0/24
and any odditional overlay networks to10.0.1.0/24
, then10.0.2.0/24
, and so on...Hopefully this helps someone out in the future, but figured I should just configure swarm to start the subnet ranges from something like
10.200.0.0/16
to reduce any conflicts in the future, as the10.0.0.0/8
block is a popular choice for VLAN subnets.The text was updated successfully, but these errors were encountered: