October 3, 20241 yr I have a docker container lets say "A". I set its 'Fixed IP address (optional)' to 172.18.0.4. This usually works fine but if i have 30 docker containers running and they all update then sometimes docker container "X" just happens to randomly get assigned 172.18.0.4. Then when "A" tries to start, it fails cuz that ip is already taken. Someone please help
October 13, 20241 yr Is the issue that you have containers talking to one another using the internal docker network and you have them referencing each other based on the docker IP? I believe the fixed IP, which shows up for me when i choose a custom bridge, is only used when you are giving the container an IP on you LAN and is not used as a way to set the internal docker IP for that container. Are you familiar with Portainer? If so, I would try setting a container specific IP in the network settings for that particular container.
October 17, 20241 yr Author Solution Not sure that works for what I’m trying to do. I’ll mark this as resolved though. I just wrote a basic bash script that checks if the docker container is up at the right ip. If not it shuts down the one that stole the ip. Launches the right one and then relaunches the thief. Should almost never actually do anything. May shut down a rogue container once a week for a few seconds during updates so whatever
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.