Is it possible to use a CIFS share as the persistence.nextcloudData.existingClaim ?

[lknite]

I saw in the log an error about setting the directory to 0700 ... for security, but I'd like to use the cifs share ... way to disable that check so it'll work anyway? This seems to prevent the use of cifs...

[jessebot]

Hi @lknite, I'm not sure what you mean about that error. Could you please post your values.yaml (after removing any sensitive data) as well as the error you're getting?

[lknite]

A CIFS share, aka a windows share (SMB), doesn't let you chmod a directory with permissions like 0700.

I have a cifs share already setup with permissions that should work, just for example we can say "global read/write by all".

Since the script is failing because 0700, rather than just issuing a warning, I haven't been able to use a CIFS share via the persistence.nextcloudData.existingClaim.

I can share my values but I'm not sure it will help. I'm using a TrueNAS server with its smb storageclass it has available called democratic-csi.

I'm curious if it's possible to use the existingClaim without trying to modify it or to generate warnings rather than errors. Mainly because I'd like to be able to work with the nextcloud data share via windows and that's more difficult with an nfs share.

[jessebot]

Sorry for the delay, but yes, please follow the issue template here when submitting an issue. This helps us evaluate what exactly is happening. Having your values.yaml shows us how helm is configuring the release, and knowing the chart version helps us see if the issue was fixed already.

The exact logs you're seeing and where you're seeing them, helps us to know where in the code base there may be an issue.

Since the script is failing because 0700, rather than just issuing a warning, I haven't been able to use a CIFS share via the persistence.nextcloudData.existingClaim.

Where is that error coming from? What script are you referring to?

I see you also mentioned not using CIFS anymore here: https://github.com/nextcloud/helm/issues/10#issuecomment-1000949271

Let me know if you'd like to close this issue in favor of us continuing to keep #10 open till others have had time to work out an exact solution.