-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Root user not created with default docker-compose.yml #904
Comments
Hey, |
I expected to be asked for the password, but I wasn't. Setting |
I have the same issue. I have a custom docker-compose for rancher-compose. I define the GITLAB_ROOT_PASSWORD and GITLAB_ROOT_EMAIL but without the expected result. As @gianmarcotoso said, it is needed to run bin/rake gitlab:production in orden to populate the DB with the admin credentials. Maybe is something missed in the Dockerfile or some script for building the image. |
I had the same issue. By manually run:
I got the error:
Maybe it's your case ? For me the value was |
This issue has been automatically marked as stale because it has not had any activity for the last 60 days. It will be closed if no further activity occurs during the next 7 days. Thank you for your contributions. |
I have followed the instructions in the quick start and, after downloading
docker-compose.yml
and setting the keys, I randocker-compose up
and waited a bit. Connecting to the Gitlab instance presented me with the login screen, but no credentials worked. Connecting to the PGSQL container I tried aSELECT COUNT(*) FROM USERS
, which resulted in a count of 0 rows.I solved the problem by running
docker-compose down
, settingGITLAB_ROOT_PASSWORD
withindocker-compose.yml
, doingdocker-compose up
and then manually running the setup by connecting to the gitlab container withdocker exec -it gitlab_gitlab_1 /bin/bash
(wheregitlab_gitlab_1
was the name of my container, got it withdocker-compose ps
) and runningbin/rake gitlab:setup
.Is this expected behavior?
The text was updated successfully, but these errors were encountered: