I have a multicontainer project in which many of the containers use different web interfaces to interact with the user, so I’ve been using nginx-proxy to automatically configure reverse proxies for the containers that need them.
However, while adding a Pi-Hole container I was not able to use the normal balena-pihole repo because while it did manage to sidestep the issue with port 53 already being used by balena-supervisor, it did that by setting pihole to only bind the port in the interface it will use, and then running the container with
network_mode: host, that way it prevents conflicts. This will not work for my setup, since nginx-proxy needs port 80 to do it’s thing, and running Pi-Hole in host mode occupies that port.
So my question is: Is there a way to make docker binding the container’s port to the host device only on a certain interface the same way pihole does from inside the container when you use the
bind-interfaces option? That way I can have pihole working in bridge mode and have it’s web interface pass through nginx-proxy like the rest of the other containers.
Thank you for any help.