-
Notifications
You must be signed in to change notification settings - Fork 265
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
chown permission in nfs pvc #588
Comments
Hi @moisesf10, thanks for submitting an Issue. 🙏
Could you point to where this is happening? Are you referring to the docker container? If so, that is controlled upstream at the nextcloud/docker repo here and here:
You'd need to open an Issue/PR for that repo if you'd like to change the container.
This has been requested before, and we're happy to review a PR for this if you'd like to submit one. |
This is not relevant for this helm chart. This is specific to your storage. For example in the nfs-csi https:/kubernetes-csi/csi-driver-nfs/blob/master/docs/driver-parameters.md Other CSIs like Trident makes a chmod and chown by default This is not a problem in nextcloud, its a problem with you're storage configuration. |
Describe your Issue
When starting the container, remove the script that performs chown and chmod operations in the /var/www/html directory.
I use an nfs server for persistence and even though I configure it with chmod 777 and groups nobody:nogroup, the container fails due to an attempt to change permissions.
Remove this and let users take care of file permissions, or add an entry to values.yaml so we can disable this functionality.
Another solution is to unlink "persistence.nextcloudData.enabled" from "persistence.enabled", as currently data persistence can only be activated if source code persistence is enabled. Unlink these options so that we can only activate data persistence and no longer have this problem
Logs and Errors
Describe your Environment
The text was updated successfully, but these errors were encountered: