Docker App Subnets/Access URLs Change on Reboot

[HappyHarvester]

I think this is more of a terminology/Googling the wrong thing issue, but I’m having some related issues:

 

Rebooting usually means that all my Docker apps have new addresses, I don’t know if these are subnet address or subdomains or something else, but the address for app A might change from https://192.168.0.116/ to https://192.168.0.118 or something like that.

 

This means that when I login via WireGuard, I usually play a guessing game to get to a given app.

 

The Overseer + *arr apps also all completely break since all of the urls I give them swap every reboot.

 

This seems like a standard enough issue, but I can’t figure out how others handle it so that you don’t have to RE tweak *arr settings every time or you can do something so you can consistently get to your apps without the bookmarks changing each time.

 

[Squid]

The internal IP address (usually 172.x.x.x) of a container is always dynamic and can never be trusted to be the same.  That's why you tend to reference via the server's IP address and an applicable port.

 

Now, if you've put the containers onto a network type of BR0, but didn't specify the actual address they should use, then yes they will get assigned a potentially new IP address every time.  Set a static IP for the container in it's template settings.