Public | Automated Build

Last pushed: 10 hours ago
Short Description
GitLab Community Edition docker image based on the Omnibus package
Full Description

GitLab Docker images

Docker Pull Command
Source Repository

Comments (81)
4 days ago

Hi all.

I want to migrate from one VPS to another with this image, what is best way to move all info?

a month ago

Almost 6000 open issues on Gitlab CE. Reason enough why they're not GitHub.

3 months ago

Hi, can you pls provide an image for ARM-architecture (Raspberry Pi 3)? Maybe this article will help:
Thanks a lot!

3 months ago

I check some image version got from
and run into the same error with

I provide some information.
Will you please check it.
If you need more information please let me know
Thank you

3 months ago

Right... their build system is a mess. It's the reason why the "Build Details" tab shows bogus data and their Dockerfile is broken. Really messy project.

You might want to search for known bugs in their issue trackers or open a new one. I suggest starting with these:

3 months ago

The error is here in dockerfile "COPY assets/wrapper /usr/local/bin/"

3 months ago

Thanks, on arriving in the bin folder, what should I do, exactly?

3 months ago

What is the path to start the server? After docker run

3 months ago

Gitlab is good, but this container is absolutely bonkers. It's not stateless at all, with directories containing both generated content and persistent stuff. The log dir is way too messy to be useful with that weird log rotator, so throw it out along with the other published volumes. And use external postgres and redis services, for the love of whatever you hold holy. (No need to have gitlab authenticate to postgres in local unix socket; just set this in pg_hba.conf and be happy: "local gitlab gitlab trust" and make sure the gitlab user has no special permissions besides login).

What I had to use to get a sane-ish persistence of only useful data was (docker-compose v2 format):
registry['storage'] = { 'filesystem' => { 'rootdirectory' => '/var/lib/registry' } }
redis['enable'] = false
gitlab_rails['redis_socket'] = "/run/redis/redis.sock"
postgresql['enable'] = false
gitlab_rails['db_adapter'] = "postgresql"
gitlab_rails['db_encoding'] = "unicode"
gitlab_rails['db_database'] = "gitlab"
gitlab_rails['db_username'] = "gitlab"
gitlab_rails['db_socket'] = "/run/postgresql/.s.PGSQL.5432"

  - '/run/postgresql:/run/postgresql:Z'
  - '/run/postgresql:/var/opt/gitlab/postgresql:Z' # necessary because of a bug where db_socket is ignored in parts of gitlab app
  - '/run/redis:/run/redis:Z'
  - '/var/lib/gitlab/builds:/var/opt/gitlab/gitlab-ci/builds:Z'
  - '/var/lib/gitlab/etc:/etc/gitlab:Z'
  - '/var/lib/gitlab/repositories:/var/opt/gitlab/git-data/repositories:Z'
  - '/var/lib/gitlab/uploads:/var/opt/gitlab/gitlab-rails/uploads:Z'
  - '/var/lib/registry:/var/lib/registry:Z'

With that, you make sure you backup your /var/lib/gitlab dir plus your postgres (which you probably already do) and maybe /var/lib/registry (this one I don't backup because it's easily rebuilt data).

After the first boot, the /etc/gitlab dir can be mounted ro and the gitlab user in postgres can lose the createdb permission.

3 months ago

There is no gitlab.rb file inside /etc/gitlab


No such file or directory @ rb_sysopen - /etc/gitlab/gitlab.rb

Is there something I am missing or the Image is having problem.