sameersbn / docker-gitlab

Dockerized GitLab
http://www.damagehead.com/docker-gitlab/
MIT License
7.9k stars 2.14k forks source link

full example of gitlab with container registry #2638

Open MehranHeydarian opened 2 years ago

MehranHeydarian commented 2 years ago

Does anyone have a complete Docker Compose of GitLab with container Registry to provide?

mschadev commented 1 year ago

my docker-compose.yml

version: '2.3'

services:
  registry:
    container_name: gitlab_registry
    image: registry
    restart: always
    expose:
      - "5000"
    ports:
      - "10500:5000"
    volumes:
      - /volume1/docker/gitlab-registry/registry:/registry
      - /volume1/docker/gitlab-registry/registry-certs:/certs
    environment:
      - REGISTRY_LOG_LEVEL=info
      - REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registry
      - REGISTRY_AUTH_TOKEN_REALM=https://YOUR_GITLAB_DOMAIN.COM/jwt/auth
      - REGISTRY_AUTH_TOKEN_SERVICE=container_registry
      - REGISTRY_AUTH_TOKEN_ISSUER=gitlab-issuer
      - REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE=/certs/registry.crt
      - REGISTRY_STORAGE_DELETE_ENABLED=true
  # ...
  gitlab:
    container_name: gitlab_web
    restart: always
    image: sameersbn/gitlab:15.5.3
   # ...
    volumes:
    - /volume1/docker/gitlab-registry/registry-certs:/certs
    environment:
    - GITLAB_REGISTRY_ENABLED=true
    - GITLAB_REGISTRY_HOST=YOUR_DOCKER_REGISTRY_DOMAIN.COM
    - GITLAB_REGISTRY_PORT=443
    - GITLAB_REGISTRY_API_URL=http://registry:5000
    - GITLAB_REGISTRY_KEY_PATH=/certs/registry.key
    # ...
FluffyDiscord commented 1 year ago

I dont know about this I get error 500 in gitlab UI and nothing in logs

danrmiller commented 1 year ago

Same, any luck or which log at what level to see the details of the 500?

danrmiller commented 1 year ago

Search the production_json.log for the request id from the 500 page, in my case it was related to a permissions error on the cert.

spatterIight commented 3 months ago

Search the production_json.log for the request id from the 500 page, in my case it was related to a permissions error on the cert.

Permissions error for me as-well, thx a bunch!