Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9611

Closed
Open
Created Sep 08, 2015 by Administrator@rootOwner

docker: rm container + run new one - fails to start if gitlab-ci is enabled

Created by: piec

Hi,

Thanks for this great projet. I recently started using gitlab, in the official docker container. I have just a few projets on it. I enabled gitlab-ci using ci_external_url, the problem is if I docker rm gitlab and docker run it again then it won't start again correctly. This is a problem if I want to change the run parameters like --restart, volumes or port redirections. In that case redisabling gitlab-ci doesn't solve the problem. I have to remove the container, disable gitlab-ci and docker run ... again.

I run my container like this:

docker run \               
    --publish 8443:443 --publish 8080:80 --publish 2222:22 \
    --name gitlab \
    --restart always \
    --add-host='gitlab.xxx.com:127.0.0.1' \
    --add-host='ci.xxx.com:127.0.0.1' \
    --volume /srv/gitlab/config:/etc/gitlab \
    --volume /srv/gitlab/logs:/var/log/gitlab \
    --volume /srv/gitlab/data:/var/opt/gitlab \
    gitlab/gitlab-ce:latest

It should be able to survive this (but doesn't):

docker rm gitlab
docker run [the same as before]

The run log can be found here. https://gist.github.com/piec/f8d886b6dc3682a45717#file-gitlab-log-L561

Issues seem related to this, but I don't know gitlab enough to understand what happens

2015-09-08_09:53:22.12901           `-._        _.-'                                           
2015-09-08_09:53:22.12902               `-.__.-'                                               
2015-09-08_09:53:22.12902 
2015-09-08_09:53:22.12903 [847] 08 Sep 09:53:22.128 # Server started, Redis version 2.8.21
2015-09-08_09:53:22.12903 [847] 08 Sep 09:53:22.128 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
2015-09-08_09:53:22.12903 [847] 08 Sep 09:53:22.128 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
2015-09-08_09:53:22.12904 [847] 08 Sep 09:53:22.128 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
2015-09-08_09:53:22.12904 [847] 08 Sep 09:53:22.129 # Fatal error loading the DB: Permission denied. Exiting.

Cheers, Pierre

Assignee
Assign to
Time tracking