Nextcloud fails to initialize when using a claim with "accessMode: ReadWriteMany" for primary persistence.
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Describe your Issue
When trying to able persistence for NextCloud, the container hangs when attempting to us emy own existing pvc's.
Logs and Errors
The container hangs with the following log:
Configuring Redis as session handler
Initializing nextcloud 26.0.1.1 ...
Describe your Environment
-
Kubernetes distribution: rke2
-
Helm Version (or App that manages helm): v3.11.3
-
Helm Chart Version: 3.5.12
My persistence section:
persistence:
# Nextcloud Data (/var/www/html)
enabled: true
existingClaim: nextcloud-html-data-claim
nextcloudData:
enabled: true
existingClaim: nextcloud-user-data-claim
Additional context, if any
It works fine if I comment out the usage of existing claims.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the hang with the shown Helm values, Kubernetes distribution, chart version, and existing claims. Inspect how the chart handles existing persistence claims and accessMode, then compare startup logs with and without those claims. Done means Nextcloud initializes successfully while using the existing claims.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100