Docker bridge address changes

[tucansam]

My server is 192.168.0.5

 

Today, I rebooted the server.

 

All of my docker containers went from 192.168.0.5:(whatever bridged ports I had defined) to 172.17.0.2, 0.3, 0.4, etc.

 

Now nothing is accessible.

ffs2-diagnostics-20190825-0033.zip

Edited August 25, 2019 by tucansam

[tucansam]

I can still access the apps, ie, 192.168.0.5:8085 brings up sab, so its at least listening on that address.  But no inter-docker communication is occurring, ie, sab is not talking to sonarr and vice versa.

[Squid]

I'm confused you're first post says that nothing was accessible via 192.x.x.x bit your next post says that they are.

The 172.x.x.x are internal ip addresses used by the containers and is quite normal and expected in bridge mode.

Sent from my NSA monitored device

[tucansam]

On previous docker screens (as in prior to yesterday), all addresses were "192.168.0.5" with their associated ports listed after that.

 

172.x.x.x is totally new to me, I have never seen it on the docker screen before.

 

I could access all of my dockers via their 192.168.0.5:<port> addresses, however none of them could talk to each other.

 

I have now given each of them their own IP address on the br1 interface, and reconfigured all of them to talk among themselves using their new addresses.  A major PITA, but its working again.

 

No idea what happened.

[bonienl]

Can you post a screenshot of the Docker page?

 

192.168.x.x addresses are likely assigned when containers are set to use a custom network (macvlan), while 172.17.x.x addresses are used as default when containers use a bridge network.

 

In other words it sounds your docker containers switched from a custom network to a bridge network. How is this possible? No clue! Normally only done by manual configuration.

 

[John_M]

Could the boot flash device have become corrupt?