Docker container - Network Unreachable

Docker Engine Swarm
,
1

Hi to all,

Please be tolerant as it is the first time I post a question here and mostly it is my first time using Docker in our company which I need to learn. At the moment I’m really new so I’m missing a lot of stuff.

This being said, we had Docker installed on Ubuntu Linux server.
Everything was working fine until I’ve been asked by IT to change a subnet conflicting to a range used for our VPN.

This subnet was the one used by docker_gwbridge which is created by default by swarm.
I tried doing what I’ve read on many places and finally got it to be change from 172.18.0.0 to 172.19.0.0

Since that time, all my containers are unhealthy and any ping attempt made to the host or any network is unreachable and I just can’t understand why.

Worse I’ve set back the docker_gwbridge to the same subnet so I can get it back working and same result…

There is something I’m missing clearly here.
Anyone has any idea or command I could use to troubleshoot further.

I used
docker network (inspect/ls/rm/create)
docker ps
route

I also restarted docker service and created deamon.json as it was inexistant but anything I do just don’t make it so I removed it also…

2

I guess you already solved the problem or started to use something else. I found your question since I moved the topic from the community category which is for asking about the community and events. In addition to using the proper category, sharing the exact command that you tried can help you get an answer sooner. In your case the issue can be many things, but one that I can think of as an example is that the created network was not an overlay network or the containers were not recreated, but I don’t think that would have been possible. Or the new ip range was in conflict with an other network.

If you could solve it, could you share how you did it so other can learn from it?