Can't launch Docker-Transmission using PIA #2459
-
a few weeks back, i updated to latest build, and immediately found that i couldn't launch Transmission, it seems it can't find the PIA ovpn file i've always used.
docker-compose.yaml:
when trying to launch i get
I can get it working if i set up PIA as an 'other' VPN, and place an au_melbourne.ovpn file in a mounted path, but not sure why the default mechanism is breaking |
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 5 replies
-
Add |
Beta Was this translation helpful? Give feedback.
-
thanks, I've added that (mapped /config path), but still throwing the same output, and not launching. I've looked through the wiki, and while it does include this config mapping, it doesn't specify any content to be added to this path, or include any provider specific settings for PIA, in fact it was working previously without it. Given the scripts in the PIA directory at https://github.com/haugene/vpn-configs-contrib/archive/main.zip, haven't been updated for 2 years, and still pull down a bunch of OVPN files, i don't think this is the issue. Since last week, I am only able to get it working if i add like this, and save an 'au_melbourne' file in the path defined
|
Beta Was this translation helpful? Give feedback.
-
You're right that the documentation is lacking provider specific option for PIA @ilike2burnthing But I'm most curious about the line with Because the config script for PIA is actually in the main image and such should be categorized as an "internal" provider: When I run the image I get:
Don't remember why it's in both places. I think I had a follow-up task to remove the scripts from the vpn-configs-contrib repo but maybe good that I didn't. The external one isn't updated as recently as the internal one though so might be some issues there as well, the port-forwarding has been fixed at least in the internal one. What host OS and Docker version are you running with @pow3rslave? |
Beta Was this translation helpful? Give feedback.
-
@haugene, i'm running Docker version 18.09.1, build 4c52b90, on Debian GNU/Linux 10 (buster), i just cleared out all old images, and culled my docker-compose file back to basics, but still same output
what if anything needs to go in the /config folder? i haven't previously run this directory, only mapped /data (which houses download dir and the /transmission dir) |
Beta Was this translation helpful? Give feedback.
-
Hitting the same issue with docker 18.09.1, running on a Raspberry Pi with Debian GNU/Linux 10 (buster)
Setting
It looks to me like an issue with
|
Beta Was this translation helpful? Give feedback.
-
Confirmed that the last working tag is 4.2, so i've pinned that in my docker compose and it's working fine somehting in the 4.3/4.31 builds must be the break |
Beta Was this translation helpful? Give feedback.
-
Sorry about the late response here, much to do at the end of the year and Christmas approaching. But now the vacation has started and I have time for some hobby projects 😉 And btw - thank you for a very generous donation @pow3rslave. Much appreciated and will be enjoyed in liquid form, one way or another ☕ 🍻 I find this issue very strange, and equally interesting. I hope we find the root cause and that it will enlighten us somehow, and not just be a boring "ah, of course" moment. Anyways - since I can't debug this locally... Can you try running the latest again and setting environment variable |
Beta Was this translation helpful? Give feedback.
-
thanks @haugene
|
Beta Was this translation helpful? Give feedback.
-
Strange, but interesting. I see this:
Note that you have an extra line with:
before it decides to use "external" mode and mine doesn't have that and then goes for "internal". Where is that coming from? |
Beta Was this translation helpful? Give feedback.
-
@gapple , does that align with what you see if you add an env. variable for DEBUG=true? |
Beta Was this translation helpful? Give feedback.
-
So... In the container on your system the file is not executable? Don't understand how that can happen. You don't have any volume mounts for that path so it's not a local override, and the revision is the same so the file should have the executable flag. Can you try running these commands?
On my machine they output:
Curious to see if there is any difference between the |
Beta Was this translation helpful? Give feedback.
-
I'm curious if there is any follow up on this issue? I'm seeing the same thing on my RPi when I run it, and, like @pow3rslave my results from running the above commands indicate that |
Beta Was this translation helpful? Give feedback.
-
Good question @kyleder, sorry about the late reply. Haven't been good at finding time for this project lately. At least I think the curve is trending upwards again 😅 I actually had these changes sitting locally, even if I had a feeling they were pushed to the dev branch 🙈 Maybe @pow3rslave can also verify and I'll get a move on and merge it to the main branch and tag a new release. It's been a while since the last one anyways. EDIT: Commit b6c4049 |
Beta Was this translation helpful? Give feedback.
-
Just updated to docker-transmission-openvpn/transmission/start.sh Lines 102 to 107 in 1103172 |
Beta Was this translation helpful? Give feedback.
Tried changing this locally and it worked, so created a PR: #2593