You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Description:
Mounted volumes in Kubernetes are always mounted with root:root (0:0) permissions. Nextcloud looks at those permissions and declares /data directory non-writeable, event if it is actually capable of writing inside this directory. Nextcloud needs to be a bit smarted and actually probe writeability OR recognize it is being ran inside container and suspend this check OR allow itself to be informed via environment variable that this check should be ignored.
As this sounds like a nice feature, the requests for this are quite low. Currently there are no plans to implement such a feature. Thus I will close this ticket for now. This does not mean we don't want this feature, but it is simply not on our roadmap for the near future. If somebody wants to implement this feature nevertheless we are happy to assist and help out.If you wish to have this feature implemented by the Nextcloud GmbH there is the option for consulting work on top of your Nextcloud Enterprise subscription to get your features implemented.
How to use GitHub
Description:
Mounted volumes in Kubernetes are always mounted with root:root (0:0) permissions. Nextcloud looks at those permissions and declares /data directory non-writeable, event if it is actually capable of writing inside this directory. Nextcloud needs to be a bit smarted and actually probe writeability OR recognize it is being ran inside container and suspend this check OR allow itself to be informed via environment variable that this check should be ignored.
Logging into container and doing "chown 33:0 data" (without -R) makes this error go away, but that's not sustainable. There is workaround with initContainers (https://stackoverflow.com/questions/43544370/kubernetes-how-to-set-volumemount-user-group-and-file-permissions), but it would be nice if Nextcloud would require no workarounds.
Steps to reproduce
Expected behaviour
No "data is writeable" error, everything works correctly.
Internally: Nextcloud probes permissions and ability to write inside /data and recognizes that all is right.
Actual behaviour
Receive "data is not writeable" error.
Internally: Nextcloud just looks at user and group owning /data and declares failure.
Server configuration
Nextcloud version: (see Nextcloud admin page)
20.0.4
Updated from an older Nextcloud/ownCloud or fresh install:
Updated.
Where did you install Nextcloud from:
hub.docker.com
Are you using external storage, if yes which one: local/smb/sftp/...
Issue with all types of mounted volumes (tested with NFS and GlusterFS).
Are you using encryption: no
The text was updated successfully, but these errors were encountered: