a multi-container Docker application to run Deluge behind a Wireguard client
WARNING: due to a docker limitation, some network traffic can escape before wireguard connects. to fix this, you should move the wireguard container to a separate compose file
- download docker-compose.yml
- put your
wg0.conf
file into./wireguard
- run
docker-compose up
if everything works correctly, Deluge should be running behind your VPN!
the Deluge web UI should be accessible at http://localhost:8112
if you want to use this persistently, you should probably
- change the locations of the
deluge-data-volume
&downloads-volume
- forward a port with your VPN provider
- (probably not required) add port forwarding to your
wg0.conf
using the rules proposed here, then set up that same port in Deluge as the incoming port. - lock the containers to specific versions using sha256 digests e.g.
linuxserver/wireguard@sha256:39dd71c3440b93b3e0343aa88b8d415cf07a43e60df208cad6e55e7d2758959e
the torrent-client
(Deluge) service shares the network stack of the vpn-sidecar
service (Wireguard), which is tunneled through your VPN provider. to maintain local connectivity to the torrent-client
container's web UI, we proxy to it to through the web-proxy
service (Nginx) using Docker container links.