I’m trying to get Qbittorrent set up within Docker on my home server and want to configure port forwarding through my VPN for all of those Linux ISOs. Ideally, I also want to get a pipeline going with the *arr stack. I’ve heard the easiest way to do this is with Gluetun but I can’t for the life of me figure it out or know how to test it. Anyone been through something similar?
Here is my current Docker Compose for reference:
services:
gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun
cap_add:
- NET_ADMIN
environment:
- VPN_SERVICE_PROVIDER=airvpn
- VPN_TYPE=wireguard
- WIREGUARD_PRIVATE_KEY="[redacted]"
- WIREGUARD_PRESHARED_KEY="[redacted]
- WIREGUARD_ADDRESSES=10.131.184.14/32
- FIREWALL_VPN_INPUT_PORTS=8069
- SERVER_COUNTRIES=United States
devices:
- /dev/net/tun:/dev/net/tun
volumes:
- /home/fenndev/.config/gluetun:/config
ports:
- 9091:9091 # WebUI
- 6881:6881
- 6881:6881/udp
restart: unless-stopped
qbit:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbit
network_mode: "service:gluetun"
environment:
- PUID=1000
- PGID=1000
- TZ=America/Los_Angeles # Timezone set to Los A>
- WEBUI_PORT=9091 # Qbittorrent webUI port
volumes:
- /home/fenndev/.config/qbit:/config # Configura>
- /home/fenndev/torrents:/downloads # Torrent da>
depends_on:
glueten:
condition: service_healthy
That’s an unknown, but welcome change. My experience for protonvpn was cludgy because you effectively had to run another service to spin and update qbittorrent’s port whenever it changed. Happy to see some form of baked in support for it now.