▲Podfox: First Container-Aware Browser(val.packett.cool)
90 points by pierremenard 14 hours ago | 6 comments
▲CGamesPlay 10 hours ago
The project being discussed in this post is https://codeberg.org/valpackett/podfox#podfox

You can actually use Traefik to do something similar using its Docker service discovery. Instead of being a SOCKS proxy, Traefik is a reverse proxy, and you can combine with `lvh.me` which resolves all subdomains to localhost. I don't use this technique any more, but a functional example command can be seen here: https://github.com/CGamesPlay/dotfiles/blob/c49e2b4ddd0fe591...

▲hobofan 5 hours ago
I think that puts it into an entirely different category. SOCKS proxies are great, as they don't require you to try and bend all domain names the correct way. In a typical intranet or proxied container cluster setup, you quickly end up hitting some application logic that e.g. returns back an absolute URL (breaking your manual usage of lvh.me), or uses non-default HTTP ports, or one of many other ways that break if you try to use a lvh.me-like setup or remapping DNS entries to localhost.
▲CGamesPlay 4 hours ago
You're correct, but in practice I never had that issue. All the applications I used this technique with were easily able to set the "site root URL" via an environment variable or something similar.

To show the other side of the coin: SOCKS proxies are less convenient, as they require you to configure your entire browser (your entire system on macOS) to use it.

▲hobofan 1 hour ago
> All the applications I used this technique with were easily able to set the "site root URL" via an environment variable or something similar

Yeah that often works, but also requires running things locally or redeploying them. For quick debugging, trying to use the service without altering it is more convenient.

> as they require you to configure your entire browser (your entire system on macOS) to use it

See my other comment. I'm on macOS, and I'm quite happy with FoxyProxy, which allows for individual pages to use a SOCKS proxy based on a regex (or just via an on/off toggle).

▲hobofan 5 hours ago
For managing SOCKS proxy usage in the browser, I can highly recommend FoxyProxy[0]. I'm using it for about a dozen different SOCKS proxy setups, and it also exists for both Firefox and Chrome, making it easy to share a similar setup with colleagues.

[0]: https://getfoxyproxy.org

▲jbverschoor 6 hours ago
I dunno. I just use orbstack and everything works. Containers have their own IP, dns, and https certificates
▲sureglymop 6 hours ago
With regular docker or podman it was always easy and useful to forward a containers port over ssh. Does anyone know how to just as easily do that (i.e. with a single command) for rootless podman?
▲yjftsjthsd-h 6 hours ago
With or without binding a host port? With a host port it should Just Work, without... I'm not sure why it wouldn't route just as well, actually; I don't think `ssh -L` acts differently than anything else, does it? Actually let me back up: What are you doing, and what does it currently do with podman?
▲sureglymop 5 hours ago
Without binding a host port. I have a remote server where my containers run and want to forward their ports directly to my local machine without binding to a host port there. That of course works with a regular bridge but not with rootless containers.
▲amarshall 10 hours ago
Unfortunately page is completely blank (iOS Safari)
▲ 4 hours ago
▲wingmanjd 10 hours ago
Blank for me too (Windows Firefox), ublock off.
▲conception 10 hours ago
Turn off your content blockers? Comes up fine for me. Or maybe add some? ;)
▲prmoustache 7 hours ago
I have firefox and content blockers and it works fine for me. On Linux.

Maybe they simply banned some user agents commonly used by IA scrapers.

▲sibilantcinder 4 hours ago
Very cool. This proxy should be a Podman feature.