I'm running multiple docker projects on my host (each in a private closed network, e.g. 172.16.x.x) and I want to expose it through a tcp proxy on my local network (127.0.0.x) for convinience (external DB tools like DBeaver/HeidiSQL/Navicat) and mysql command line clients.
The *.local.domain.tld is just an A-Record pointing to 127.0.0.1..
I basically need a tcp reverse proxy solution that I can automate on environment start and stop.
I know HAproxy and nginx (to some extent) can handle TCP routing, but it's a massive overhead I'd like to avoid.
I've updated my reply. What you're trying to achieve is not the intended usage of PrxPass (at least at the moment). You want to expose your hosts docker network to your local network and I guess you can do that by setting up a VPN tunnel to your host.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm running multiple docker projects on my host (each in a private closed network, e.g. 172.16.x.x) and I want to expose it through a tcp proxy on my local network (127.0.0.x) for convinience (external DB tools like DBeaver/HeidiSQL/Navicat) and mysql command line clients.
The *.local.domain.tld is just an A-Record pointing to 127.0.0.1..
I basically need a tcp reverse proxy solution that I can automate on environment start and stop.
I know HAproxy and nginx (to some extent) can handle TCP routing, but it's a massive overhead I'd like to avoid.
I've updated my reply. What you're trying to achieve is not the intended usage of PrxPass (at least at the moment). You want to expose your hosts docker network to your local network and I guess you can do that by setting up a VPN tunnel to your host.