One for your Transmission configuration files and another for your downloads. Inside the docker folder, create a folder named transmission-openvpn In your root directory, create a folder named Downloads Create Adapter and Configuration File. Other Docker containers can also use this same method that the proxy server used to use the NordVPN connection with the -net=container:nordvpn3 argument. Just adjust it to the name of your NordVPN container. Hey Guys, Looking to maybe get some advice/assistance on getting the Deluge/Transmission docker to work with OpenVPN from NordVPN. I spent the last couple of days trying to get something to work, but the closest that I got was I could set up Deluge and run the Proxy pointed to NordVPN's servers. It is possible to use the NordVPN Linux CLI app within a Docker container. In order to do that, you have to use the following NordVPN Dockerfile configuration to set up your Docker container.
Official NordVPN client in a docker container; it makes routing traffic through the NordVPN network easy. How to use this image 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).
I've recently taken to using Docker to install and run various softwareon my home server. Something that so far, it excels at - the people atlinuxserver.io are doing great work! I've had a rocky time with Docker inthe past after having had it foisted upon me for development work, which I didnot enjoy, but I can see the benefits for certain situations.
I found myself needing to run the traffic from one particular container(Jackett) over a VPN connection so that it could by-pass country-specificrestrictions. As a noob Docker user, this caused some confusion, but I eventuallystumbled upon the
--net
parameter to docker create
and run
.Using this parameter it's possible to tell a container to use the network ofanother. You can run an OpenVPN client container, which will initiate a secureconnection, and configure other containers to use its network. The beauty ofthis setup is that you don't need to learn or manage any complicated
ip_tables
rules or any other network configuration, you can just point one container atanother and have the traffic secured.All I needed now was a suitable Docker image. Eventually, I got lucky andfound an image that supported my exact VPN provider, NordVPN.
This is how I created and started the OpenVPN container. Once this was running,a secure VPN connection was established to NordVPN.
Most of these options are standard, but the
-p 9117:9117
parameter on line 5needs explanation. This is the port mapping that Jackett uses by default. Whenwe use another container's network it's necessary to expose the port(s) that ourother containers use on the VPN container.And here is how I setup Jackett to use the VPN container. The relevant line is
--net=container:vpn
. Note that I don't have a -p 9117:9117
line here like Iwould if I was not using --net=container:vpn
.Now I can access Jackett at
http://<host-ip>:9117
and all traffic will be sentthrough the VPN container's network!Nordvpn Synology
I've recently taken to using Docker to install and run various softwareon my home server. Something that so far, it excels at - the people atlinuxserver.io are doing great work! I've had a rocky time with Docker inthe past after having had it foisted upon me for development work, which I didnot enjoy, but I can see the benefits for certain situations.
I found myself needing to run the traffic from one particular container(Jackett) over a VPN connection so that it could by-pass country-specificrestrictions. As a noob Docker user, this caused some confusion, but I eventuallystumbled upon the
--net
parameter to docker create
and run
.Using this parameter it's possible to tell a container to use the network ofanother. You can run an OpenVPN client container, which will initiate a secureconnection, and configure other containers to use its network. The beauty ofthis setup is that you don't need to learn or manage any complicated
ip_tables
rules or any other network configuration, you can just point one container atanother and have the traffic secured.All I needed now was a suitable Docker image. Eventually, I got lucky andfound an image that supported my exact VPN provider, NordVPN.
Docker Transmission Nordvpn 2
This is how I created and started the OpenVPN container. Once this was running,a secure VPN connection was established to NordVPN.
Most of these options are standard, but the
-p 9117:9117
parameter on line 5needs explanation. This is the port mapping that Jackett uses by default. Whenwe use another container's network it's necessary to expose the port(s) that ourother containers use on the VPN container.And here is how I setup Jackett to use the VPN container. The relevant line is
--net=container:vpn
. Note that I don't have a -p 9117:9117
line here like Iwould if I was not using --net=container:vpn
.Docker Transmission Nordvpn Download
Now I can access Jackett at
http://<host-ip>:9117
and all traffic will be sentthrough the VPN container's network!