docker compose is appreciated
$ cat Projects/qbittorrent/docker-compose.yml version: "2.1" services: qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent environment: - PUID=1000 - PGID=1000 - TZ=Europe/Berlin - WEBUI_PORT=8081 volumes: - /path/to/appdata/config:/config - /home/username/Downloads/Torrents:/downloads ports: - 8081:8081 - 6881:6881 - 6881:6881/udp restart: unless-stoppedThe whole server is running under the VPN.
I’ve pushed up my setup to Gitlab if you’d like to check it out! I use it with ProtonVPN, but can be adapted to be used with others.
seems the link is broken
I use gluetun with sabnzbd
Not torrent tech but yeah.I often read about not using two containers but instead to use a combi docker.
I tried formatting it on here but it doesn’t work.
gluetun + qBit
The compose file creates both and binds qBit to gluetun. I also have port forwarding set up through AirVPN.
This is the way, look no further
Does this only tunnel qbittorrent through the VPN or all traffic on the device?
Have exactly the same setup:
It tunnels everything that is bound to the same network (see the line with gluetun within the qbittorrent container.
And for anyone using a reverse proxy: that can run against the gluetun container with the bound containers port. (edit: in OPs example gluetun:8090 for qbittorrent web)
Only qbit I have other stuff in that stack as well, like sonarr and radarr, that I cut out.
The network mode setting in docker acts as a bind. The port is exposed to the host in gluetun. If gluetun throws an error and shuts down, qBit WebUI is no longer accessible.
qmcgaw/gluetun + ghcr.io/onedr0p/qbittorrent
binhex/arch-qbittorrentvpn
