Docker ARR Stack with Gluetun VPN
Budget: $10 – $30 USD
I’m putting together a small ARR stack in Docker and need an expert to wire everything so that every outbound request from Prowler and Radar is forced through a Gluetun VPN container.
My host is already running Docker on Linux; what I’m missing is a clean, reproducible Compose (or Swarm) setup that:
• Spins up Gluetun first, using my WireGuard credentials and built-in kill-switch.
• Launches Prowler and Radar as separate services but attaches them to the Gluetun network so they inherit its VPN tunnel for all traffic.
• Exposes only the essential web UI ports on the host while keeping search, tracker and metadata queries safely behind the tunnel.
• Survives restarts with proper health-checks and dependencies so nothing leaks when the VPN drops.
Deliverables
1. A commented docker-compose.yml (or equivalent) covering Gluetun, Prowler, and Radar.
2. Any custom scripts, env files, or firewall tweaks needed for DNS leaks prevention.
3. A brief step-by-step README that lets me reproduce the setup on another machine and verify traffic is truly routed through Gluetun (curl/ip checks).
If you’ve already tamed similar media stacks or have clever tricks for container-level routing, I’d love to see them. Let me know roughly how long you’ll need once you’ve seen my current folder layout and VPN provider details.
My host is already running Docker on Linux; what I’m missing is a clean, reproducible Compose (or Swarm) setup that:
• Spins up Gluetun first, using my WireGuard credentials and built-in kill-switch.
• Launches Prowler and Radar as separate services but attaches them to the Gluetun network so they inherit its VPN tunnel for all traffic.
• Exposes only the essential web UI ports on the host while keeping search, tracker and metadata queries safely behind the tunnel.
• Survives restarts with proper health-checks and dependencies so nothing leaks when the VPN drops.
Deliverables
1. A commented docker-compose.yml (or equivalent) covering Gluetun, Prowler, and Radar.
2. Any custom scripts, env files, or firewall tweaks needed for DNS leaks prevention.
3. A brief step-by-step README that lets me reproduce the setup on another machine and verify traffic is truly routed through Gluetun (curl/ip checks).
If you’ve already tamed similar media stacks or have clever tricks for container-level routing, I’d love to see them. Let me know roughly how long you’ll need once you’ve seen my current folder layout and VPN provider details.