26.0.0.x (helm chart
Operating system and version: docker
Hi all, did anyone manage to deploy Nextcloud on K8S, using EFS as the primary storage? The docs say that a
ReadWriteMany filesystem is required, but simply using that results in this bug, and after a couple of hours I just gave up.
Maybe I missed the one way this would have worked, and others have found it – so … anyone?
All my helm value files contained something around this:
persistence: enabled: true size: 1Gi storageClass: efs-sc accessMode: ReadWriteMany nextcloudData: # will ONLY work if persistence.enabled == true as well. # ...
Steps to replicate it:
- use helm with the above config snippet (or adjust this pastebin to your needs)
- watch the error from this link appear
The output of your Nextcloud log in Admin > Logging: nextcloud is not coming up.
The output of your config.php file in
/path/to/nextcloud: unchanged to standard install with
ReadWriteOnce persistance enabled.
The output of your Apache/nginx/system log in
Output errors in nextcloud.log: irrelevant, the error is caused by
entrypoint.sh it seems.