Goodbye Port Conflicts: Podman Without Port Forwarding and Containerizing Dev Environments for CLI Addicts
Frustrated by port conflicts, the author abandoned container port forwarding and instead uses Podman and a Rust-based SOCKS proxy called Podfox to enable direct browser communication with the Podman network. Podfox bypasses the need for host DNS configuration, resolving container hostnames and using Podman network information to locate the gateway address for DNS queries and proxying. The author also shares their experience streamlining command-line development environment containerization using Homebrew and a custom fish script called Podchamp. By mounting the Homebrew prefix and setting environment variables, the same development tools are readily available across different containers without rebuilding images or installing dependencies, boosting efficiency.