-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling .persistence.enabled
leads to /var/www/html/lib
and probably other files not being created
#583
Comments
I think I'm having this issue as well. Whenever I try to do an upgrade, my |
#584 this issue just got transferred here, maybe it is related? |
Same issue here, meaning I cannot access the nextcloud instance at all as the pod goes into a CrashLoopBackOff status |
In my case I'm pretty sure its my NFS StorageClass that is at fault here. I'm getting abysmally slow read times (but not write) for some reason that I cannot replicate outside the container. Doing I was able let the entrypoint script finish running by creating another Nextcloud container without the liveness probes to prevent timing out before (eventually) finishing. There were a lot of volume mounts, so I just pulled the generated Deployment yaml from my helm install using EDIT: |
Adding the following to my livenessProbe:
initialDelaySeconds: 7200
readinessProbe:
initialDelaySeconds: 7200
startupProbe:
initialDelaySeconds: 7200 |
Describe your Issue
Whenever persistence is enabled,
/var/www/html/lib
and probably other files are not created. This leads to crashing and errors. I'm using NFS on all the volumes which could be making it slower and losing a data race somewhere.Logs and Errors
Describe your Environment
Kubernetes distribution: self hosted MicroK8s v1.28.9 revision 6750
Helm Version (or App that manages helm): helm v3.15.1
Helm Chart Version: 5.0.0
values.yaml
:The text was updated successfully, but these errors were encountered: