Docker-transmission-openvpn: Downloading to network drive

[leebillington]

Really new at this, so sorry if I'm missing something obvious.

Got everything working properly on Ubuntu, but am having difficulty getting the downloads where I want them, and I'm sure it's a syntax error on my part.

I have a network drive "dlink/Volume_1" mapped as "dlink" in Ubuntu. How does the file location need to be formatted to get it to store here instead of within the Docker container?

[mrjackyliang]

I believe the code below solves your issue. Closing for now. Let me know if there are any problems.

-v /dlink/Volume_1/:/data

[leebillington]

Thanks @mrjackyliang

I think I'm still missing something though. I just tested and it's still placing the downloads in /data within the container, not on the external drive. Here's my full container:

docker run --cap-add=NET_ADMIN --restart=always -d
-v /dlink/Volume_1/:/data
-e CREATE_TUN_DEVICE=true
-e OPENVPN_PROVIDER=PIA
-e OPENVPN_CONFIG=US Houston
-e OPENVPN_USERNAME=*
-e OPENVPN_PASSWORD=*
-e WEBPROXY_ENABLED=false
-e LOCAL_NETWORK=10.10.1.0/24
-e TRANSMISSION_WEB_UI=combustion
--log-driver json-file
--log-opt max-size=10m
--dns 8.8.8.8
--dns 8.8.4.4
-p 9091:9091
haugene/transmission-openvpn

[mrjackyliang]

I remember @haugene stating that putting files on a network drive doesn't really work? I'll let him explain.

On Jul 25, 2019, at 6:29 PM, Lee Billington [e-mail] wrote:

Thanks @mrjackyliang

I think I'm still missing something though. I just tested and it's still placing the downloads in /data within the container, not on the external drive. Here's my full container:

docker run --cap-add=NET_ADMIN --restart=always -d
-v /dlink/Volume_1/:/data
-e CREATE_TUN_DEVICE=true
-e OPENVPN_PROVIDER=PIA
-e OPENVPN_CONFIG=US Houston
-e OPENVPN_USERNAME=*
-e OPENVPN_PASSWORD=*
-e WEBPROXY_ENABLED=false
-e LOCAL_NETWORK=10.10.1.0/24
-e TRANSMISSION_WEB_UI=combustion
--log-driver json-file
--log-opt max-size=10m
--dns 8.8.8.8
--dns 8.8.4.4
-p 9091:9091
haugene/transmission-openvpn

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[leebillington]

Nevermind, I was able to find my mistake. it wasn't /dlink/Volume_1 but rather home/elbert/dlink

[haugene]

Glad you got it working. The network drive issues are related to the "watch" folder if I remember correctly. Something about the inotify hooks transmission use to detect new torrent files that have been tricky on NFS shares and such. Storing there should be OK. And I think the watch-directory stuff is addressed someplace else in the transmission configs. A new option was added that scans it (I think). Someone can shout out if they need more details, all I got for now :)