-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transmission permission denied #64
Comments
Hi @gwicksted, Yes, I believe I know the issue and a solution. I really should mention this in the docs. The transmission docker image (https://hub.docker.com/r/linuxserver/transmission) supports user & group variables so content is downloaded with those values. For example, this is what I have in my
This makes all the downloads have user id 1000 and group id 1000. After you make the change don't forget to restart the transmission container. Let me know if this works for you. |
That definitely solved the 911:911 user and group issue on the download folder. However, even though the permissions now look perfect, it's still getting the same error. I force recreated the transmission docker image. After it failed, I even tried setting the transmission user and password in nefarious settings UI (not sure if that matters?) but again same error. So I cleared it and retried - same error. So I stopped all containers and started them all again. Still failed. This is what the folder looks like now (which is perfect):
I never see it create a file (or even a dot directory) under either folder while downloading. Transmission shows this in the details:
when it gets this error:
A different one shows this:
when it gets this error:
Any thoughts where to go next? I have the suggested change applied to the docker-compose but that is the only difference from stock. I see this with ps aux:
.env is:
transmission-settings.json is:
docker-compose.yml (partial - just showing transmission):
|
If it helps, viewing the docker logs, it shows it couldn't create the folder itself due to permission denied... but it already exists.
|
I think I may know the issue. The abstraction that docker introduces with volumes from the host to container can start to get pretty confusing. I believe your issue is that you edited I think the line that's tripping you up is:
Since you told transmission to download to However, I suggest reverting Try that and restarting transmission via the force-restart method. Here's a quick docker host/container volume explanation. Every container has it's "own filesystem". So, in this case, transmission downloads to |
You got it! Thanks!! I learned a lot since the start of this ticket. Willing to contribute. Possibly a .env for the PUID/PGID as well as some documentation. |
Nice! Yeah, I learned a lot too along the way with this project. Glad you got it sorted out. |
Issue appears to be related to transmission user id / group id but I'm unsure how to solve.
911:911
which is the uid:gid used as a placeholder when something goes wrongI'm a software dev but generally unfamiliar with docker and transmission.
Context: running in a debian 10 minimal vm inside proxmox using the instructions from this git repo to install.
The text was updated successfully, but these errors were encountered: