NordVpn official client in a docker. It makes routing containers traffic through NordVpn easy.
This container was designed to be started first to provide a connection to other containers (using --net=container:vpn, see below Starting an NordVPN client instance).
NOTE: More than the basic privileges are needed for NordVPN. With docker 1.2 or newer you can use the --cap-add=NET_ADMIN and --device /dev/net/tun options. Earlier versions, or with fig, and you'll have to run it in privileged mode.
docker run -ti --cap-add=NET_ADMIN --cap-add=SYS_MODULE --device /dev/net/tun --name vpn \
--sysctl net.ipv4.conf.all.rp_filter=2 \
-e USER=user@email.com -e PASS='pas$word' \
-e CONNECT=country -e TECHNOLOGY=NordLynx -d bubuntux/nordvpn
Once it's up other containers can be started using it's network connection:
docker run -it --net=container:vpn -d some/docker-container
However to access them from your normal network (off the 'local' docker bridge), you'll also need to run a web proxy, like so:
sudo docker run -it --name web -p 80:80 -p 443:443 \
--link vpn:<service_name> -d dperson/nginx \
-w "http://<service_name>:<PORT>/<URI>;/<PATH>"
Which will start a Nginx web server on local ports 80 and 443, and proxy any requests under / to the to http://<service_name>:/. To use a concrete example:
sudo docker run -it --name bit --net=container:vpn -d dperson/transmission
sudo docker run -it --name web -p 80:80 -p 443:443 --link vpn:bit \
-d dperson/nginx -w "http://bit:9091/transmission;/transmission"
For multiple services (non-existant 'foo' used as an example):
sudo docker run -it --name bit --net=container:vpn -d dperson/transmission
sudo docker run -it --name foo --net=container:vpn -d dperson/foo
sudo docker run -it --name web -p 80:80 -p 443:443 --link vpn:bit \
--link vpn:foo -d dperson/nginx \
-w "http://bit:9091/transmission;/transmission" \
-w "http://foo:8000/foo;/foo"
The environment variable NETWORK must be your local network that you would connect to the server running the docker containers on. Running the following on your docker host should give you the correct network: ip route | awk '!/ (docker0|br-)/ && /src/ {print $1}'
docker run -ti --cap-add=NET_ADMIN --device /dev/net/tun --name vpn \
-p 8080:80 -e NETWORK=192.168.1.0/24 \
-e USER=user@email.com -e PASS='pas$word' -d bubuntux/nordvpn
Now just create the second container without the -p parameter, only inlcude the --net=container:vpn, the port should be declare in the vpn container.
docker run -ti --rm --net=container:vpn -d bubuntux/riot-web
now the service provided by the second container would be available from the host machine (http://localhost:8080) or anywhere inside the local network (http://192.168.1.xxx:8080).
version: "3"
services:
vpn:
image: bubuntux/nordvpn
cap_add:
- NET_ADMIN # Required
- SYS_MODULE # Required for TECHNOLOGY=NordLynx
sysctls:
- net.ipv4.conf.all.rp_filter=2
devices:
- /dev/net/tun # Required
environment: # Review https://github.com/bubuntux/nordvpn#environment-variables
- USER=user@email.com # Required
- "PASS=pas$word" # Required
- CONNECT=United_States
- TECHNOLOGY=NordLynx
torrent:
image: linuxserver/qbittorrent
network_mode: service:vpn
depends_on:
- vpn
web:
image: dperson/nginx # https://github.com/dperson/nginx
links:
- vpn:torrent
depends_on:
- torrent
tmpfs:
- /run
- /tmp
- /var/cache/nginx
ports:
- 80:80
- 443:443
command: -w "http://torrent:8080/;/"
# The torrent service would be available at http://localhost/
version: "3"
services:
vpn:
image: bubuntux/nordvpn
network_mode: bridge # Required
cap_add:
- NET_ADMIN # Required
- SYS_MODULE # Required for TECHNOLOGY=NordLynx
sysctls:
- net.ipv4.conf.all.rp_filter=2
devices:
- /dev/net/tun # Required
environment: # Review https://github.com/bubuntux/nordvpn#environment-variables
- USER=user@email.com # Required
- "PASS=pas$word" # Required
- CONNECT=United_States
- TECHNOLOGY=NordLynx
- NETWORK=192.168.1.0/24
ports:
- 8080:8080
torrent:
image: linuxserver/qbittorrent
network_mode: service:vpn
depends_on:
- vpn
# The torrent service would be available at https://localhost:8080/ or anywhere inside the local network http://192.168.1.xxx:8080
All traffic going through the container is router to the vpn (unless whitelisted), If connection to the vpn drops your connection to the internet stays blocked until the VPN tunnel is restored. THIS IS THE DEFAULT BEHAVIOUR AND CAN NOT BE DISABLE.
USER- User for NordVPN account.PASS- Password for NordVPN account, surrounding the password in single quotes will prevent issues with special characters such as$.CONNECT- [country]/[server]/[country_code]/[city]/[group] or [country] [city], if none provide you will connect to the recommended server.- Provide a [country] argument to connect to a specific country. For example: Australia , Use
docker run --rm bubuntux/nordvpn sh -c "nordvpnd & sleep 1 && nordvpn countries"to get the list of countries. - Provide a [server] argument to connecto to a specific server. For example: jp35 , Full List
- Provide a [country_code] argument to connect to a specific country. For example: us
- Provide a [city] argument to connect to a specific city. For example: 'Hungary Budapest' , Use
docker run --rm bubuntux/nordvpn sh -c "nordvpnd & sleep 1 && nordvpn cities [country]"to get the list of cities. - Provide a [group] argument to connect to a specific servers group. For example: P2P , Use
docker run --rm bubuntux/nordvpn sh -c "nordvpnd & sleep 1 && nordvpn groups"to get the full list. - --group value, -g value Specify a server group to connect to. For example: 'us -g p2p'
- Provide a [country] argument to connect to a specific country. For example: Australia , Use
TECHNOLOGY- Specify Technology to use:- OpenVPN - Traditional connection.
- NordLynx - NordVpn wireguard implementation (3x-5x times faster). NOTE: Requires
--cap-add=SYS_MODULEand--sysctl net.ipv4.conf.all.rp_filter=2
PROTOCOL- TCP or UDP (only valid when using OpenVPN).OBFUSCATE- Enable or Disable. When enabled, this feature allows to bypass network traffic sensors which aim to detect usage of the protocol and log, throttle or block it (only valid when using OpenVpn).CYBER_SEC- Enable or Disable. When enabled, the CyberSec feature will automatically block suspicious websites so that no malware or other cyber threats can infect your device. Additionally, no flashy ads will come into your sight. More information on how it works: https://nordvpn.com/features/cybersec/.DNS- Can set up to 3 DNS servers. For example 1.1.1.1,8.8.8.8 or Disable, Setting DNS disables CyberSec.WHITELIST- List of domains that are gonna be accessible outside vpn (IE rarbg.to,yts.am).NETWORK- CIDR networks (IE 192.168.1.0/24), add a route to allows replies once the VPN is up.NETWORK6- CIDR IPv6 networks (IE fe00:d34d:b33f::/64), add a route to allows replies once the VPN is up.TZ- Set a timezone (IE EST5EDT, America/Denver, full list).GROUPID- Set the GID for the vpn.DEBUG- Set to 'on' for troubleshooting (User and Pass would be log).PORTS- Semicolon delimited list of ports to whitelist for both UDP and TCP. For example- PORTS=9091;9095
This image use docker manifest for multi-platform awareness, simply pulling bubuntux/nordvpn should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
| Architecture | Tag |
|---|---|
| x86/i686 | i386 |
| Linux x86-64 | amd64 |
| ARMv5 32-bit | armv5e |
| ARMv7 32-bit | armv7hf |
| ARMv8 64-bit | aarch64 |
If you have any problems with or questions about this image, please contact me through a GitHub issue.