Docker-transmission-openvpn: Run the container without the VPN

[niXta1]

This question has been up before.
But now I agree that there should be a way to disable the VPN part. Because even if I use another VPN docker (azinchen/nordvpn, zero maintenance, and 100% servers availability), I would still like to use this.
There are other transmission dockers, but none of them are as good as this. For example, the included transmission-web-control.

Alternatively, this approach can be integrated into this: #655
But that is much more work.

[haugene]

Making vpn optional is a bigger rewrite no matter how we do it, but the holidays are coming up so it might be a good time to do it. Would be nice if more people have time to contribute to the rewrite and/or testing. And this would be a breaking change, so I propose a 3.0-beta tag for a while.

First we should discuss how we want this to work, and if we should separate transmission entirely (also tinyproxy?). Although it seems that having them bundled is what most people want.

It's also a hassle to keep ovpn configs up to date. If all providers had a good and reliable URL to fetch them from we could do it build time. But I'm concerned that dynamically downloading 40 zip files will fail of networking reasons too often.

[edgd1er]

Could it be a good idea not to provide vpn files but have an empty ovpn folder and download based on OPENVPN_PROVIDER value (well, for vpn provider that have a download conf url )? at reboot could be a good moment to update files ? emptying the folder would force a new download.

as for a disable vpn switch, the question is why use another openvpn image ? what is missing/incorrect in yours, avantage, disavantage ? what could be changed ? for the moment, I'm very happy with your container using nordvpn, but I don't have a 24/24 7/7 usage.
For what I have understood, you would have an image for tinyproxy, one for transmission (yours) and one for openvpn (yours or another). everything would be tied through a docker-compose ?

[niXta1]

The nordvpn container above works fine, I dont think downloading ovpn files on demand should be a problem.

I just use —network=”container:vpn” to connect.

[haugene]

Marking this as a "won't fix" for now. I think it's a cool idea and could be useful exactly for those scenarios, but it's outside the scope at least for me to make the improvement.

[dev-ddoe]

I know this issue is closed, but I was facing the same issue. I just to share my solution somewhere.
On my side it was possible using the following code change:
```diff --git a/openvpn/start.sh b/openvpn/start.sh
index 38cd9515f..bfef59765 100755
--- a/openvpn/start.sh
+++ b/openvpn/start.sh
@@ -11,8 +11,10 @@ if [[ "${CREATE_TUN_DEVICE,,}" == "true" ]]; then
fi

if [[ "${OPENVPN_PROVIDER}" == "None" ]] || [[ -z "${OPENVPN_PROVIDER-}" ]]; then

• echo "OpenVPN provider not set. Exiting."
• exit 1
• # Hack to not use th vpn
• dockerize -template /etc/transmission/environment-variables.tmpl:/etc/transmission/environment-variables.sh
• /etc/openvpn/tunnelUp.sh x x x 0.0.0.0
• sleep infinity
  elif [[ ! -d "${VPN_PROVIDER_CONFIGS}" ]]; then
  echo "Could not find OpenVPN provider: ${OPENVPN_PROVIDER}"
  echo "Please check your settings."
  ```