Replies: 1 comment
-
|
I haven't been able to get it working. I'm using Longhorn with NFS volume mounted as ReadWriteMany, but I'm getting this error: Big Pickle (AI model) says "The issue is that NEXTCLOUD_INIT_LOCK was removed from the Nextcloud Docker image in newer versions. The current image (32.0.5) always uses flock, which doesn't work on NFS-backed RWX volumes." I don't want to pin to an older version to work around this... Does anyone have nextcloud running with multiple replicas? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I want to run Nextcloud in a highly available configuration. Part of that would be to increase
replicaCountbeyond 1.Clearly the chart supports this. Unfortunately, I haven’t been able to find any official documentation that assures me that running multiple replicas of Nextcloud is supported or safe from an application point of view. 1, 2 Importantly: if it's at all supported, perhaps the exact details of the configuration matter – I have no idea.
For example, perhaps it supports multiple replicas when using an S3 backend but not with PVC storage. Or perhaps multi-part uploads require some special configuration to avoid collisions before the resulting file has been finalized. Or something with file locking or background jobs or something else. I would love to know if there are any caveats for how to make multiple replicas work safely, or if it's always safe. 🙂
It might seem silly to ask this when the chart has a
replicaCountparameter , but I've been bitten before by chart parameters introducing unsafe behavior. Knowing the application's safety guarantees is important in this context, and I've not been able to get much details regarding this for Nextcloud.Looking forward to some input on this.
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions