UI doesn't display registry container tag when using external registry

Summary

We recently configured gitlab container registry on our gitlab on premises server, using an external docker registry on the same private network.

Everything is working well expect the fact that the tags are not displayed on gitlab UI and API.

image

It is if we use the docker API.

docker images registry-gitlab.toto.titi/test/traefik
REPOSITORY                                      TAG       IMAGE ID       CREATED         SIZE
registry-gitlab.toto.titi/test/traefik   latest    ddb0268e5b5f   14 months ago   92.4MB

Steps to reproduce

  • Navigate to a project which have container registry images
  • Click on Packages & Registries > Container Registry
  • Select the Image
  • The message "This image has no active tags" is displayed despite the fact that the image has at least a tag

Example Project

Not possible as the issue is present only on our on premises instance.

What is the current bug behavior?

None of the tags images are listed (0 tags)

What is the expected correct behavior?

Image tags should be displayed

Relevant logs and/or screenshots

See summary section

Output of checks

/

Results of GitLab environment info

gitlab version 14.9.2-ce.0 omnibus

Here is our configuration in /etc/gitlab/gitlab.rb :

registry_external_url 'https://registry-gitlab.toto.titi'
registry_nginx['ssl_certificate'] = <PATH TO SSL CERT>
registry_nginx['ssl_certificate_key'] = <PATH TO SSL KEY>
gitlab_rails['registry_enabled'] = true
gitlab_rails['registry_api_url'] = "http://192.168.0.10:5000"
gitlab_rails['registry_issuer'] = "gitlab-issuer"
gitlab_rails['registry_host'] = "registry-gitlab.toto.titi"

Here is the external registry configuration :

version: 0.1
storage:
  filesystem:
    rootdirectory: /var/lib/registry
  delete:
    enabled: true
http:
  addr: 0.0.0.0:5000
auth:
  token:
    realm: https://gitlab.titi.toto/jwt/auth
    service: container_registry
    issuer: gitlab-issuer
    rootcertbundle: <PATH TO SSL CERT>

We found some clues here : #277472 (closed)

But we are unable to apply the requested configuration (replacing '0.0.0.0' by 'localhost'), as the registry is not on the same server as our gitlab instance.

We have been unable to find any similar case in gitlab bug/issues.

Thank you very much

Assignee Loading
Time tracking Loading