-
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
Issue on starting Gitlab #28
Comments
@gargkapil2008 Please check if your host meets the hardware requirements. Could be a RAM issue. Gitlab requires at least 1 GB of available RAM. |
I am running this docker on my vagrant box. I will check for ram issue. Thanks
|
closing issue.. |
@sameersbn The issue is still there as i have increased RAM to 2GB but it is not working:
Maybe i am doing something wrong with ports! |
@gargkapil2008 you dont need to send the command sudo service gitlab start The gitlab server is started automatically. docker logs -f gitlab P.S. Please refer the README |
Can you send me the exact command needed to run the container file. As I am
|
docker pull sameersbn/gitlab
docker run -rm -i -t -name=gitlab -p 8080:80 sameersbn/gitlab wait for the application to start, it could take a while to start. Point your web browser to http://127.0.0.1:8080 |
Thanks a lot @sameersbn ! Just a one more concern how can i ssh into container, I haven't configured authorized_keys. I have got the password from gitlab logs using this : Container info: |
@gargkapil2008 the instructions i sent you are the bare minimum to just get the application started. If you want to use the container in an actual production environment them you need to read the readme. Infact, the commands I sent you are from the quick start section of the readme. You will need to forward the ssh ports for SSH access from outside the guest using the -p option. |
/etc/init.d/gitlab start
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US)
Removing stale Unicorn web server pid. This is most likely caused by the web server crashing the last time it ran.
Removing stale Sidekiq web server pid. This is most likely caused by the Sidekiq crashing the last time it ran.
Starting both the GitLab Unicorn and Sidekiq/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US)
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US)
The GitLab Unicorn web server with pid 261 is running.
The GitLab Sidekiq job dispatcher with pid 271 is running.
GitLab and all its components are up and running.
root@f329b2e4c9a2:~# master failed to start, check stderr log for details
The text was updated successfully, but these errors were encountered: