Make sure to promote some to manager before removing the final "old" manager. Is there anywhere else docker likes to keep a cache or any info?ĮDIT: The "solution" is to remove nodes 1 at a time and adding them back to the swarm after changing their IP address. I've covered all my bases in /etc/hosts, nf and /etc/network/interfaces.
Also even though the swarm is running with this change, DNS resolution between containers and on the overlay network doesn't work properly. Changing this file manually seems to work but after a host reboot it reverts to the original IP addresses.
I did find a file in /bar/lib/docker/swarm/state.json which contains the same IP addresses listened for the managers as when running docker info. Is it possible to have the hosts have their IP addresses change and keep the same swarm intact? I've done a bunch of research and haven't found much info online. How do Docker networks work The IP address uses 4 bytes and splits them to a network ID and a host ID. The base establishes a network, and the size cuts it into more pieces.
These containers must be identifiable by unique IP addresses with calls over port 80. These Docker containers will share one host that has one physical NIC. Here, the default-address-pools option allows us to define a set of custom IP subnets. &0183 &32 How do I configure Docker containers to have unique IP addresses that are not the default ones The Docker containers will run Apache or some web service. Looking for some help regarding the IP addresses of managers in a swarm. &0183 &32 Docker uses the daemon.json file to change the docker defaults.