January 14, 20242 yr There must be a better way. I run several dockers from the arr suite and these communicate with each other. For this I use bridge mode, and access them on my LAN via the mapped ports on my Unraid IP. However - for the dockers that must communicate with eachother, this IP apparently does not work. No worries though: So I use the Docker Internal IP in their 172.17.0.x network. All good, until the order of the dockers changes. And the problem is that this network assigns IPs based on the startup order. When the order changes because a new one is added/started before the others, the docker instances can not reach the other instances. * I find it quite inconvenient that when installing Apps, it adds the docker to the top of the start list. It all seems ok, but after a reboot it gets started before the others, and breaks many dockers.
January 15, 20242 yr Solution There is a better way. Create a user-defined custom bridge network, and then instead of using the IP address just use the hostname (container name).
January 16, 20242 yr Author Thanks, going to try this. And probably also need to adjust “Preserve user defined networks” docker settings. Still a feature to have new dockers start last (instead of first) would be nice to keep things consistent by default.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.