January 6, 20233 yr Having an issue where I changed my IP address schema, and docker seems to hold on to the old IP address for port mappings on containers that were installed at the time. For example, if I install new or clean install existing docker (e.g., delete appdata folder) the old IP address is gone and everything is okay. Otherwise, docker seems to retain the old scheme in the port mappings. I've looked around and been unable to find a fix for this, or understanding if it is a bug. I've attached a screenshot for an example showing what I mean, but unclear how to even determine the issue. First and last items are *wrong* as they existed before I changed the IP scheme Middle one is *right* but I had to uninstall the docker, delete the directory in appdata, and re-install to get to this point. Any thoughts or advice? Logs I need to pull?
January 6, 20233 yr No, your conclusions are wrong a bit, no need to worry. "its not a bug, its a feature 😁" What you see is the difference between "host" and "bridge" mode of the dockers. In Hostmode the docker works on the real IP of the UNRAID Box, in Bridgemode the docker spans an own LAN (172.17... and 172.18 (invisible here)) and maps the ports to the main LAN through this "bridge". Bridgemode also installs an internal route.
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.