Cannot start container #91
Comments
|
@auraltension try deleting the folder rm -rf /opt/gitlab/data/tmp
docker run --name='gitlab' -it --rm --link postgresql:postgresql \
-p 10022:995 -p 10080:8080 \
-e "DB_USER=gitlab" -e "DB_PASS=rOrUQUqCvPLqEL8PSwC9a" -e "DB_NAME=gitlabhq_production" \
-e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" \
-v /opt/gitlab/data:/home/git/data \
sameersbn/gitlab:latest |
|
@auraltension if it does not work, paste the output of the above command in this thread |
|
Thanks for the response I looked up the 'instance method "LOCK"' warning and theres an issue thread in Gitlab, but they claim it is a warning and gitlab should still work ? |
|
@auraltension is that the end of the output? |
|
Yeah, That ^ is a complete copy of my terminal. Confirmed by docker logs. |
|
@auraltension that does not look right. I am not able to pinpoint what could be the issue you are facing so we might have to do a few tests. First, can you confirm if the instructions in the quick start guide works for you and you have a working gitlab instance? docker run --name='gitlab' -i -t --rm \
-p 10022:22 -p 10080:80 \
-e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" \
sameersbn/gitlab:7.0.0If it works, I suggest you delete the docker run --name='gitlab' -i -t --rm \
-p 10022:22 -p 10080:80 --link postgresql:postgresql \
-e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" \
sameersbn/gitlab:7.0.0 app:rake gitlab:setupand then this command to start the container: docker run --name='gitlab' -i -t --rm \
-p 10022:22 -p 10080:80 --link postgresql:postgresql \
-e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" \
sameersbn/gitlab:7.0.0If this still does not work, I recommend you paste the logs of the above commands here. |
|
@auraltension another thing. can you tell me which postgresql image you are using? meaning is it sameersbn/postgresql or some other? |
|
ohh after spotting the following in my syslog I think this actually may be caused by my grsecurity patched kernel: There is no /usr/bin/ruby2.1 on the host system so I guess this is within the container. I'll get a chance to play much later tonight and update the thread. |
|
I rolled to a non grsecurity patched kernel and then started getting different issues. First, to add to my above comment, that syslog I had been from running the quickstart command set. And yes, I'm using the latest sameersbn/postgresql. The OS is Debian 7.5, on a Xen based VPS. I realised this may be useful also As I'm on a Linode VPS I rolled to one of their kernels, and tried again. First, I rm'd gitlab, and tried again with my original full run command, which also failed, but with one extra line of output: I then went back to basics, but now everything had started to respond with a chpasswd error. Relevant syslog Last section of strace I did a quick google and saw an issue you had raised in regards to this, so this may be better in another issue thread. It's intertesting that docker worked this first time after switching kernels, but now errors out. Tried rebooting but no joy. I'm now left wondering how to proceed, Linode claim docker works well, and their users seem to largely concur. The postgres is working. I'm thinking of switching back to my custom kernel and compare configs with those of the Ubuntu versions which had been claimed to have solved this latest issue, and doesing a bit of grsecurity forum reading. Will keep you posted. |
|
Oh, it seems that issue was not solved by upgrading the host, but the container ubuntu version. hrmm |
|
@auraltension what did you change the container ubuntu version to? one thing, you may want to use the latest gitlab image in which I have removed the use of chpasswd command so the above chpasswd related issue will not show. |
|
@auraltension I have a feeling that the linode vps is has disabled the container networking and enabled host networking for docker. The above chpasswd error is a know error when host networking is used. But since the latest image |
|
Sorry, I didn't upgrade the container image. I was referencing the issue you had raised elsewhere. I'm off to bed and so will tinker more over the weekend. |
|
Went back to the stock Linode kernel and tried with latest. Results in the 'su: Sustem error' issue I wish I knew how to get better info for you. |
|
@auraltension looks like a selinux issue. try disabling selinux and retry. |
|
I see on moby/moby#6345 that people are having similar issues with 3.15. I will try a Linode 3.14 kernel this evening and report back. Also, I have no selinux nor apparmor. |
|
I used an earlier kernel version and it all worked fine. |
|
@auraltension glad you got it resolved. |
|
@auraltension closing.. please reopen if required |
|
Thanks for closing, I see Docker will be putting out a release which includes the fix for the 3.15 issues in early august. |
Hi. Maybe I'm missing something obvious, but I'm new to docker and also gitlab. I can't get the container to start.
First, thanks for the great resources, I started with your postgres image and that worked really well.
In short I run 'run', it shows briefly in ps and then disappears.
/var/log/docker can be found at:
https://gist.github.com/auraltension/412f1b13d3342f43579e#file-gistfile1-txt
docker run --name='gitlab' -i -t --rm --link postgresql:postgresql -e "DB_USER=gitlab" -e "DB_PASS=rOrUQUqCvPLqEL8PSwC9a" -e "DB_NAME=gitlabhq_production" -p 10022:995 -p 10080:8080 -e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" -v /opt/gitlab/data:/home/git/data sameersbn/gitlab:latest app:rake gitlab:setup
User: root Password: deih7eey9uKo
Starting openssh server...
Starting redis server...
Running gitlab rake task...
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
This will create the necessary database tables and seed the database.
You will lose any previous data stored in the database.
Do you want to continue (yes/no)? yes
gitlabhq_production already exists
-- enable_extension("plpgsql")
-> 0.0351s
-- create_table("broadcast_messages", {:force=>true})
-> 0.0410s
-- create_table("deploy_keys_projects", {:force=>true})
....
-- initialize_schema_migrations_table()
-> 0.0013s
Adding limits to schema.rb for mysql
== Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
2014-06-30T12:48:07Z 191 TID-epb7s INFO: Sidekiq client with redis options {:url=>"redis://localhost:6379", :namespace=>"resque:gitlab"}
Administrator account created:
login.........admin@local.host
password......5iveL!fe
docker run --name='gitlab' -d --link postgresql:postgresql -e "DB_USER=gitlab" -e "DB_PASS=rOrUQUqCvPLqEL8PSwC9a" -e "DB_NAME=gitlabhq_production" -p 10022:995 -p 10080:8080 -e "GITLAB_PORT=10080" -e "GITLAB_SSH_PORT=10022" -v /opt/gitlab/data:/home/git/data sameersbn/gitlab:latest
af05128da659f9c56ef730ce843cb631e551b797d20e6e56ddda2ac3a976fda4
root@jake:/home/auraltension# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
027c3589a4d8 sameersbn/gitlab:latest /app/init app:start 6 seconds ago Up 6 seconds 22/tcp, 443/tcp, 80/tcp, 0.0.0.0:10022->995/tcp, 0.0.0.0:10080->8080/tcp gitlab
root@jake:~# docker attach gitlab
2014/06/30 12:53:48 You cannot attach to a stopped container, start it first
root@jake:/home/auraltension# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
root@jake:~# docker logs gitlab
User: root Password: Uzu4mi6ua9Eh
Starting openssh server...
Starting redis server...
Starting nginx...
Migrating database...
Compiling assets. Please be patient, this could take a while...
Instance method "lock!" is already defined in ActiveRecord::Base, use generic helper instead or set StateMachine::Machine.ignore_method_conflicts = true.
The text was updated successfully, but these errors were encountered: