sameersbn / sameersbn/docker-gitlab

registry with docker-compose not working

Open
#2,237 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Has somebody a working docker-compose.yaml where a nginx proxy is in front of and registry is working fine?

It's not possible to make that work actually.

  gitlab:
    restart: unless-stopped
    image: sameersbn/gitlab:13.4.2
    depends_on:
    - redis
    - postgresql
    healthcheck:
      test: ["CMD", "/usr/local/sbin/healthcheck"]
      interval: 5m
      timeout: 10s
      retries: 3
      start_period: 5m
    external_links:
    - "registry:registry.domain.at"
    ports:
    - "10080:80"
    - "10022:22"
    volumes:
    - /srv/docker-compose/data/gitlab/gitlab:/home/git/data:Z
    - /srv/docker-compose/data/gitlab/certs:/certs
    - /srv/docker-compose/data/gitlab/gitlab-logs:/var/log/gitlab
    environment:
    # ....
    # ....
    - GITLAB_REGISTRY_ENABLED=true
    - GITLAB_REGISTRY_HOST=registry.domain.at
    - GITLAB_REGISTRY_PORT=443
    - GITLAB_REGISTRY_API_URL=http://registry:5000
    - GITLAB_REGISTRY_KEY_PATH=/certs/registry.key
    - GITLAB_REGISTRY_CERT_PATH=/certs/registry.crt
    - GITLAB_REGISTRY_ISSUER=gitlab-issuer
    - GITLAB_REGISTRY_GENERATE_INTERNAL_CERTIFICATES=true


  registry:
    restart: unless-stopped
    image: registry:2
    depends_on:
    - gitlab
    ports:
    - "5000:5000"
    external_links:
    - "gitlab:gitlab.domain.at"
    volumes:
    - /srv/docker-compose/data/gitlab/registry:/registry
    - /srv/docker-compose/data/gitlab/certs:/certs
    environment:
    - REGISTRY_LOG_LEVEL=info
    - REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY=/registry
    - REGISTRY_AUTH_TOKEN_REALM=https://git.domain.at/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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the posted docker-compose service definitions and the GitLab registry environment variables; reproduce the failure with nginx in front of the registry. Compare the GitLab and registry connectivity, certificate, and token settings shown in the issue. Done requires a confirmed working compose configuration, but the issue does not name a test or repository file.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, nginx
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.