chown permission in nfs pvc about helm HOT 2 OPEN

Hi @moisesf10, thanks for submitting an 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.

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:

• alpine container: https://github.com/nextcloud/docker/blob/95c49292109eb561630b3b5ffc88e3b039812239/Dockerfile-alpine.template#L116-L117
• debian container: https://github.com/nextcloud/docker/blob/95c49292109eb561630b3b5ffc88e3b039812239/Dockerfile-debian.template#L121-L122

You'd need to open an Issue/PR for that repo if you'd like to change the container.

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

This has been requested before, and we're happy to review a PR for this if you'd like to submit one.

from helm.

This is not relevant for this helm chart. This is specific to your storage.

For example in the nfs-csi https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/docs/driver-parameters.md
You can simply enable a changemod before mounting it the first time.

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.

from helm.