-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Init fails on chown for NFS directories #214
Comments
I can confirm, same config and same issue |
Give |
I still have the same issue with your image above:
|
I can confirm it's working for the |
i'm still having issues on |
Same here, I'm also still having the same issue on |
I'm going to assume you're doing some kind of permission squashing that means the remote volume reports the wrong permissions to the container, so it thinks it needs chowning. There's a limit to what we can do here, we don't want to have the container init when it can't set up the environment properly for it to work OOTB for most users, and we can't possibly detect every possible weird setup and know that it's OK. The simplest solution is just don't use |
I don't do anything specific, I have a mount which is from a synology nas which has ACLs. There's nothing fancy in that. What would make sense would be either to:
I don't quite understand why you need to own the folders. What's the point of doing that? The container only needs to be able to write, you don't need to own the folder for that. Case in point, it worked fine before. |
@thespad That's correct, I export the NFS shares on the host (proxmox) using I agree with @gotson, I don't understand the change(s) made in 3.00-r6-ls139 that prevent On
|
To be honest, your use case represents a very tiny percentage of our user base. And by that I don't mean nfs users because I also use nfs, but because I set it up properly, I don't experience the issue you're facing. So if you have any constructive feedback, or any ideas that can fix your issue while not negatively impacting the other users' experience, we're all ears. |
An environment variable to keep the previous behaviour. |
I understand that you don't want to make exceptions for "a tiny percentage" of your user base. I was just wondering why the change was made, and what the requirement of the Regardless, I'll use the solution suggested by @thespad going forward, when I decide to update to > If know a good guide on how to "properly set up" NFS, please share. Thanks |
It's not that we don't want to make exceptions, it's a matter of maintaining a balance between increased workload and not wanting to impact other users. Implementing additional measures increases our workload and we already have a huge backlog of bug fixes and improvements. Chown is necessary and crucial for the majority of our users. Removing it breaks it for many so it's not acceptable as a solution. The change is not something we did specifically. It's due to a behavior change in the supervisor we use, which got updated from v2 to v3 (lots of changes, pretty much a rewrite). Not something that can be reverted with an env variable. |
Wouldn't it be possible to not perform the chown if a specific environment variable is present, similar as what's been done in https://github.com/linuxserver/docker-transmission/pull/215/files ? |
I'm one of the tiny percentage of users (by running the image on K8s with NFS PersistentVolume-s). I've worked around the issue by:
NFS share and files there mount with correct permissions. Note also commit https://github.com/linuxserver/docker-mods/pull/521/files |
@aptalca any thoughts on this? |
Still happens on latest with completely standard NFS mounts and correct permissions. I don't understand how to implement the workarounds suggested here. |
Please open a new issue. Many changes have been made since this one |
Expected Behavior
Transmission should work correctly with mounted NFS folder.
(it was working correctly for version linuxserver/transmission:3.00-r5-ls138)
Current Behavior
init-transmission-config
fails onchown
for complete and incomplete folders:Steps to Reproduce
download
folder (or mounted complete/incomplete folders inside download) as download volumeEnvironment
OS: Ubuntu 22.04 LXC on Proxmox
CPU architecture: x86_64
How docker service was installed:
Command used to create docker container (run/create/compose/screenshot)
Docker logs
The text was updated successfully, but these errors were encountered: