nofi: An interruption-free notification system for Linux
github.com
Fair point, I've updated the readme now.
Honestly, I'd be surprised if static IPs fix it. Docker's default network type (bridge network) is very good at assigning IPs to containers without clashing, even with container restarts and replacements: it's been battle tested for years in production use. As others have said, standard DNS hostnames of containers should be sufficient. But I'll certainly be interested to hear your results.
In the above example I've declared a Docker Bridge network with the range
172.20.0.0/24
and a gateway at172.20.0.1
. I have a service namedapp
with a static IP of172.20.0.10
.The same is also possible with IPv6, though there are extra steps involved to make IPv6 networking work in Docker and it's not enabled by default so I won't go into detail in this comment.
Out of curiosity, what's the use case for a static IP in the Docker Bridge network? Docker compose assigns hostnames equal to the service name. That is, if you had another container in the
app
network from my example above, it could just do a DNS lookup forapp
and it would resolve to172.20.0.10
.