GitLab 11.0.4 fails to start after docker image update

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Today after update from 11.0.3 to 11.0.4 with docker-compose gitlab was unable to start.

docker-compose.yml

gitlab-ce:
  image: 'gitlab/gitlab-ce:latest'
  restart: always
  hostname: 'example.com'
  container_name: gitlab
  environment:
    GITLAB_OMNIBUS_CONFIG: |
      external_url 'https://example.com'
      registry_external_url 'https://example.com'      
      gitlab_rails['registry_enabled'] = true
      registry_nginx['listen_https'] = false
      registry_nginx['listen_port'] = 5007
      gitlab_rails['gitlab_shell_ssh_port'] = 9022
      nginx['listen_port'] = 80
      nginx['listen_https'] = false
  ports:
    - '127.0.0.1:8082:80'
    - '127.0.0.1:5000:5007'
    - '9022:22'
  volumes:
    - '/srv/gitlab/config:/etc/gitlab'
    - '/srv/gitlab/logs:/var/log/gitlab'
    - '/srv/gitlab/data:/var/opt/gitlab'

update command:

docker-compose stop && docker-compose rm && docker-compose pull && docker-compose up -d

docker logs gitlab-ce

Preparing services...
/opt/gitlab/embedded/bin/runsvdir-start: line 37: /proc/sys/fs/file-max: Read-only file system
Starting services...
Configuring GitLab package...
Configuring GitLab...
<internal:gem_prelude>:8:in `rescue in <internal:gem_prelude>': uninitialized constant Gem::LoadError (NameError)
	from <internal:gem_prelude>:5:in `<internal:gem_prelude>'

After downgrading to gitlab-ce:11.0.3-ce.0 image all is OK.

Edited Jun 23, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading