Container registry error "repository name not known to registry"

Infrastructure as Code & Cloud Native
,
1

Hi,

I have some problem while pushing to container registry.
it is showing {“errors”:[{“code”:“NAME_UNKNOWN”,“message”:“repository name not known to registry”

on docker container logs.
is there something I miss while setting up?

Regards,
Andre

2

Hi @razerlock86 are you pushing to the GitLab registry or an external one like Docker Hub?

Sarah

3

Hi Sarah,

Yes I meant to push it to Gitlab Container Registry.
I was using Gitlab CE on my company server. Already activated the registry on the gitlab.rb, but I cannot push image to it

4

Right, I’m just wondering whether you’ve run into a bug in GitLab. For some reason the issues page keeps returning errors for me, but I think this is the query you want:

5

Hi Sarah,

Thank you for answering, but I cannot access the issues page, keeps returning errors for me eithers.

6

btw this is my setup on the gitlab omnibus

registry_external_url 'https://xxxxx:5050'

### Settings used by GitLab application
gitlab_rails['registry_enabled'] = true
gitlab_rails['registry_host'] = "https://xxxxx"
gitlab_rails['registry_port'] = "5050"
gitlab_rails['registry_path'] = "/var/opt/gitlab/gitlab-rails/shared/registry"

# Notification secret, it's used to authenticate notification requests to GitLab application
# You only need to change this when you use external Registry service, otherwise
# it will be taken directly from notification settings of your Registry
# gitlab_rails['registry_notification_secret'] = nil

###! **Do not change the following 3 settings unless you know what you are
###!   doing**
gitlab_rails['registry_api_url'] = "http://localhost:5000"
gitlab_rails['registry_key_path'] = "/var/opt/gitlab/gitlab-rails/certificate.key"
gitlab_rails['registry_issuer'] = "omnibus-gitlab-issuer"

### Settings used by Registry application
registry['enable'] = true
registry['username'] = "registry"
registry['group'] = "registry"
# registry['uid'] = nil
# registry['gid'] = nil
# registry['dir'] = "/var/opt/gitlab/registry"
registry['registry_http_addr'] = "localhost:5000"
registry['debug_addr'] = "localhost:5001"
registry['log_directory'] = "/var/log/gitlab/registry"
registry['env_directory'] = "/opt/gitlab/etc/registry/env"
registry['env'] = {
    "REGISTRY_HTTP_RELATIVEURLS" => true,
#   'SSL_CERT_DIR' => "/opt/gitlab/embedded/ssl/certs/"
}
registry['log_level'] = "info"
registry['log_formatter'] = "text"
registry['rootcertbundle'] = "/var/opt/gitlab/registry/certificate.crt"
registry['health_storagedriver_enabled'] = true
registry['storage_delete_enabled'] = true
registry['validation_enabled'] = false
registry['autoredirect'] = true
registry['compatibility_schema1_enabled'] = false

Is there something that I missed?

7

I’m afraid I only use GitLab SASS, so I don’t know about Omnibus, but I did get the issues list to work in an incognito window (hmm!):

  • This issue suggests You need to enable delete in docker registry. This solves the problem - this was linked from here
  • This one I think is probably not relevant to you?
  • This issue seems to have a really strange work-around which was related to this issue on moving projects between groups

Hopefully that gives you a starting point!

Sarah

8

Hi Sarah,

Thank you for the help, I can push to container registry now, it seems I cannot use the same domain as the gitlab so I change to the subdomain and now it’s working.

Regards,
Andreas

9

Right, I think that makes sense - if your project is in a group or a subgroup, all sorts of things like pages will be in subdomains.

Regards,

Sarah