I’ve made progress here running
socat in the background and configuring it to bind to
[::] (with and tunnel those to
socat TCP6-LISTEN:8020,bind=[::],reuseaddr,ipv6only=1,fork TCP4:127.0.0.1:8020 &
Once I get things working I’ll figure out what sort of PR might make sense to file with the
I also ended up using
docker compose to create a sort of “tunneled” environment to run the container within locally. It requires a bit of acrobatics to make it work, but I think it’s the simplest approach, all things considered.
For each service on fly I want to connect to, I run an additional service in
docker-compose.yml. I also use the
--exit-code-from option on
docker compose up, which tears everything down cleanly after my ephemeral container finishes executing.
This approach would be even cleaner if
flyctl proxy accepted a --bind argument that let me bind it to something other than
127.0.0.1. (In this specific setting I would prefer