-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Setting up Postgres database on first install doesn't input details correctly #257
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can you test with the new image released today?
|
I'm experiencing the same issue on version I was using nextcloud-maintained docker image and those environment variables worked there (I didn't see a message in the web UI warning me about using sqlite and I was able to set an admin username/password). I guess this is something specific to their docker image and not the app itself. |
Our container isn't configurable via env variables. |
Expected Behavior
Inputting postgres database details on the first boot should correctly pass details to the config.php file.
Current Behavior
Inputting postgres database details on the first boot results in the NextCloud administrator account details being used as the postgres user, and the postgres database name gets "oc_" appended to the front. These details are verified in the config.php file and need to be manually fixed.
Steps to Reproduce
Environment
OS: Ubuntu 21.10 and Ubuntu 22.04 as the host
CPU architecture: arm64
How docker service was installed: via kubernetes as a StatefulSet
Command used to create docker container (run/create/compose/screenshot)
Kubernetes statefulset on K3S
Docker logs
Nil logs of this event.
I have tried this twice on different occasions and it has stumped me. I'm not sure if it's an upstream NextCloud issue or if it's specific to this container.
The text was updated successfully, but these errors were encountered: