I hate it when a containerized project expects you to pass its public IP address in an ENV variable within the docker file or compose.
What if the public IP is dynamic and the host is NATed?
Dear fellow selfhosters, how do you address that?
I hate it when a containerized project expects you to pass its public IP address in an ENV variable within the docker file or compose.
What if the public IP is dynamic and the host is NATed?
Dear fellow selfhosters, how do you address that?
@multifact easy, I don’t use that software 😅
But in all seriousness I’ve never seen such a requirement. Do you spot it often? I’ve got nearly 30 services self hosted with docker on k3s and have never seen such an environment variable. Some have had public domain/uri, but never IP.