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.
`version: “3” services: gluetun: image: qmcgaw/gluetun container_name: Gluetun restart: unless-stopped cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=airvpn - SERVER_COUNTRIES=Netherlands volumes: - C:\Docker Configs\Gluetun:/gluetun
qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qBitTorrent restart: unless-stopped environment: - TZ=PST - WEBUI_PORT=8090 volumes: - C:\Docker Configs\qBitTorrent:/config - M:\Media:/media
network_mode: service:gluetunTrying to format this nicely but I can’t get code format to work.
gluetun + qBit
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.
This is the way, look no further