-
Notifications
You must be signed in to change notification settings - Fork 273
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
Postrgresql need to be started first while using externalDatabase #42
Comments
I can confirm, nextcloud installation is broken if external postgresql deployed with this chart is used. @billimek ping |
wrboyce
added a commit
to wrboyce/nextcloud-helm
that referenced
this issue
Feb 24, 2021
wrboyce
added a commit
to wrboyce/nextcloud-helm
that referenced
this issue
Feb 24, 2021
Fixes nextcloud#42 Signed-off-by: Will Boyce <me@willboyce.com>
menardorama
pushed a commit
to menardorama/helm
that referenced
this issue
May 13, 2021
Fixes nextcloud#42 Signed-off-by: Will Boyce <me@willboyce.com> Signed-off-by: Thomas Menard <menardorama@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found that if Postgresql is not running before the nextcloud docker image is launched, I get some weird issues:
nextcloud-values.yml:
Sometimes I get the setup screen of nextcloud (asking to create a new admin account), sometimes I just get an error code 503 indefinitely.
If I take the same value and I deploy the bitnami postgresql chart manualy (using the same config) and then I deploy nextcloud (with
postgresql.enable = false
this time) everything works great.Currently, I have a script which does 2 deployments with a sleep in between to resolve this issue
The text was updated successfully, but these errors were encountered: