Application
Deluge website
OpenVPN website
Privoxy website
Description
Deluge is a full-featured BitTorrent client for Linux, OS X, Unix and Windows. It uses libtorrent in its backend and features multiple user-interfaces including: GTK+, web and console. It has been designed using the client server model with a daemon process that handles all the bittorrent activity. The Deluge daemon is able to run on headless machines with the user-interfaces being able to connect remotely from any platform. This Docker includes OpenVPN to ensure a secure and private connection to the Internet, including use of iptables to prevent IP leakage when the tunnel is down. It also includes Privoxy to allow unfiltered access to index sites, to use Privoxy please point your application at http://<host ip>:8118
.
Build notes
Latest stable Deluge release from Arch Linux repo. Latest stable OpenVPN release from Arch Linux repo. Latest stable Privoxy release from Arch Linux repo.
Usage
docker run -d \
--cap-add=NET_ADMIN \
-p 8112:8112 \
-p 8118:8118 \
-p 58846:58846 \
-p 58946:58946 \
--name=<container name> \
-v <path for data files>:/data \
-v <path for config files>:/config \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=<yes|no> \
-e VPN_USER=<vpn username> \
-e VPN_PASS=<vpn password> \
-e VPN_REMOTE=<vpn remote gateway> \
-e VPN_PORT=<vpn remote port> \
-e VPN_PROTOCOL=<vpn remote protocol> \
-e VPN_DEVICE_TYPE=<tun|tap> \
-e VPN_PROV=<pia|airvpn|custom> \
-e VPN_OPTIONS=<additional openvpn cli options> \
-e STRONG_CERTS=<yes|no> \
-e ENABLE_PRIVOXY=<yes|no> \
-e LAN_NETWORK=<lan ipv4 network>/<cidr notation> \
-e NAME_SERVERS=<name server ip(s)> \
-e DEBUG=<true|false> \
-e UMASK=<umask for created files> \
-e PUID=<UID for user> \
-e PGID=<GID for user> \
binhex/arch-delugevpn
Please replace all user variables in the above command defined by <> with the correct values.
Access Deluge
http://<host ip>:8112
Access Privoxy
http://<host ip>:8118
PIA provider
PIA users will need to supply VPN_USER and VPN_PASS, optionally define VPN_REMOTE (list of gateways https://www.privateinternetaccess.com/pages/client-support) if you wish to use another remote gateway other than the Netherlands.
PIA example
docker run -d \
--cap-add=NET_ADMIN \
-p 8112:8112 \
-p 8118:8118 \
-p 58846:58846 \
-p 58946:58946 \
--name=delugevpn \
-v /apps/docker/deluge/data:/data \
-v /apps/docker/deluge/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=yes \
-e VPN_USER=myusername \
-e VPN_PASS=mypassword \
-e VPN_REMOTE=nl.privateinternetaccess.com \
-e VPN_PORT=1198 \
-e VPN_PROTOCOL=udp \
-e VPN_DEVICE_TYPE=tun \
-e VPN_PROV=pia \
-e STRONG_CERTS=no \
-e ENABLE_PRIVOXY=yes \
-e LAN_NETWORK=192.168.1.0/24 \
-e NAME_SERVERS=8.8.8.8,8.8.4.4 \
-e DEBUG=false \
-e UMASK=000 \
-e PUID=0 \
-e PGID=0 \
binhex/arch-delugevpn
AirVPN provider
AirVPN users will need to generate a unique OpenVPN configuration file by using the following link https://airvpn.org/generator/
- Please select Linux and then choose the country you want to connect to
- Save the ovpn file to somewhere safe
- Start the delugevpn docker to create the folder structure
- Stop delugevpn docker and copy the saved ovpn file to the /config/openvpn/ folder on the host
- Start delugevpn docker
- Check supervisor.log to make sure you are connected to the tunnel
AirVPN example
docker run -d \
--cap-add=NET_ADMIN \
-p 8112:8112 \
-p 8118:8118 \
-p 58846:58846 \
-p 58946:58946 \
--name=delugevpn \
-v /apps/docker/deluge/data:/data \
-v /apps/docker/deluge/config:/config \
-v /etc/localtime:/etc/localtime:ro \
-e VPN_ENABLED=yes \
-e VPN_REMOTE=nl.vpn.airdns.org \
-e VPN_PORT=443 \
-e VPN_PROTOCOL=udp \
-e VPN_DEVICE_TYPE=tun \
-e VPN_PROV=airvpn \
-e ENABLE_PRIVOXY=yes \
-e LAN_NETWORK=192.168.1.0/24 \
-e NAME_SERVERS=8.8.8.8,8.8.4.4 \
-e DEBUG=false \
-e UMASK=000 \
-e PUID=0 \
-e PGID=0 \
binhex/arch-delugevpn
Notes
Default password for the webui is "deluge"
User ID (PUID) and Group ID (PGID) can be found by issuing the following command for the user you want to run the container as:-
id <username>
The STRONG_CERTS environment variable is used to define whether to use strong certificates and enhanced encryption ciphers when connecting to PIA (does not affect other providers).
If you appreciate my work, then please consider buying me a beer :D