chown permission in nfs pvc

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

Initializing nextcloud 29.0.3.4 ...
rsync: [generator] chown "/var/www/html/." failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/.patches" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/ext" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS/CRT" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS/CRT/Auth" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS/CRT/HTTP" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS/CRT/IO" failed: Operation not permitted (1)
rsync: [generator] chown "/var/www/html/3rdparty/aws/aws-crt-php/src/AWS/CRT/Internal" failed: Operation not permitted (1)

Describe your Environment

helm install ..........
--set persistence.enabled=true \ #enabled just to make "persistence.nextcloudData.enabled" work
--set persistence.storageClass="nfs-client-production" \
--set persistence.accessMode="ReadWriteMany" \
--set persistence.nextcloudData.enabled=true \
--set persistence.nextcloudData.size="50Gi" \
--set persistence.nextcloudData.accessMode="ReadWriteMany" \
--set persistence.nextcloudData.storageClass="nfs-client-producao" \

Start with values.yaml and trace the chart templates that configure persistence and the container startup behavior. Compare the current persistence.enabled and persistence.nextcloudData.enabled relationship with the requested NFS use case. Done means an NFS-backed data volume can be enabled without the failing permission changes, while the rendered Helm configuration remains valid.