You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Using your example docker compose with the reverse proxy works perfectly, but what happens if I want to use two containers that insist on using the same port? And worse, they both want to use port 80? Since I’m using networkmode: “service:vpn”, I can’t map the ports at a container level, only at the wireguard-PIA level. Any thoughts?
The text was updated successfully, but these errors were encountered:
If the two services are hardcoded to bind to port 80, then all I can think of would be running a second vpn container for the second service. They could still be attached to the same Docker bridge network if they need to communicate with each other, although it might be a bit fiddly as Docker's internal dns would no longer be used for resolving container names.
Have you got an example compose showing what you're trying to do? If the issue isn't what I'm thinking of, then there might be an easier way of working around it.
Hi! Using your example docker compose with the reverse proxy works perfectly, but what happens if I want to use two containers that insist on using the same port? And worse, they both want to use port 80? Since I’m using
networkmode: “service:vpn”
, I can’t map the ports at a container level, only at the wireguard-PIA level. Any thoughts?The text was updated successfully, but these errors were encountered: