Issue on starting Gitlab

[gargkapil2008]

/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

[sameersbn]

@gargkapil2008 Please check if your host meets the hardware requirements. Could be a RAM issue. Gitlab requires at least 1 GB of available RAM.

[gargkapil2008]

I am running this docker on my vagrant box. I will check for ram issue.

Thanks
On Mar 8, 2014 12:30 AM, "Sameer Naik" notifications@github.com wrote:

Please check if your host meets the hardware requirements. Could be a RAM
issue

Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-37055834
.

[sameersbn]

closing issue..

[gargkapil2008]

@sameersbn The issue is still there as i have increased RAM to 2GB but it is not working:

vagrant@precise64:~$ docker ps
CONTAINER ID        IMAGE                   COMMAND             CREATED             STATUS              PORTS                                                   NAMES
1338a4d98f34        local/jenkins:latest    /usr/sbin/sshd -D   2 days ago          Up 19 seconds       0.0.0.0:49154->22/tcp, 0.0.0.0:8080->8080/tcp           tender_poincare     
f329b2e4c9a2        kapil/gitlab:latest   /usr/sbin/sshd -D   2 days ago          Up 18 seconds       0.0.0.0:49153->22/tcp, 0.0.0.0:8086->8080/tcp, 80/tcp   loving_fermi        
vagrant@precise64:~$ ssh root@0.0.0.0 -p 49153
Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-33-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

Last login: Mon Mar 10 06:14:02 2014 from 172.17.42.1
-bash: warning: setlocale: LC_ALL: cannot change locale (en_US)
root@f329b2e4c9a2:~# sudo service gitlab start
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.....
The GitLab Unicorn web server with pid 110 is running.
The GitLab Sidekiq job dispatcher with pid 124 is running.
GitLab and all its components are up and running.
root@f329b2e4c9a2:~# master failed to start, check stderr log for details

Maybe i am doing something wrong with ports!

[sameersbn]

@gargkapil2008 you dont need to send the command

sudo service gitlab start

The gitlab server is started automatically.
Please start the docker image and watch the logs

docker logs -f gitlab

P.S. Please refer the README

[gargkapil2008]

Can you send me the exact command needed to run the container file. As I am
new to this.
On Mar 10, 2014 6:50 PM, "Sameer Naik" notifications@github.com wrote:

Reopened #28 #28.

Reply to this email directly or view it on GitHubhttps://github.com//issues/28
.

[sameersbn]

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

[gargkapil2008]

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 :
docker logs gitlab 2>&1 | grep '^User: ' | tail -n1

Container info:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 473d91fff198 kapil/gitlab:latest /gitlab/gitlab app:s 22 minutes ago Up 22 minutes 0.0.0.0:8085->80/tcp, 22/tcp

[sameersbn]

@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.