Proxy Docker Registry Fails to pull

806 views
Skip to first unread message

Sverre Moe

unread,
Mar 9, 2021, 2:48:24 PM3/9/21
to Nexus Users
I need some help making sense of some problem I am experiencing with Nexus Docker proxy.

I have set up 2 Docker Registry proxies

SUSE: https://registry.suse.com
HTTPS Connector 38382
Allow anonymous docker pull
Docker Index: Use proxy registry

Docker Hub: https://registry-1.docker.io
HTTPS Connector 38383
Allow anonymous docker pull
Docker Index: Use Docker Hub

I got the Docker Hub registry URL from this documentation:
https://help.sonatype.com/repomanager3/formats/docker-registry/proxy-repository-for-docker

All these are combined within a Docker Group along with our own internal hosted Docker registry. This group has HTTPS Connector on port 38380.

When I try to pull from the proxied registries directly.

Pulling directly from SUSE proxy:
docker pull nexus.company.com:38382/suse/sle15:15.2
15.2: Pulling from suse/sle15
f3d2df4815db: Pulling fs layer
error pulling image configuration: unauthorized: access to the requested resource is not authorized

Pulling from Docker Hub proxy:
docker pull nexus.company.com:38383/opensuse/leap:15.2
Error response from daemon: unauthorized: access to the requested resource is not authorized


Each docker repository has Anonymous pull toggled, and I have the Docker Bearer Token Realm in Realms.

I have even tried docker login, but that does not help. Not logged in it cannot find resource, logged in I get unauthorized. My user is admin so I have every rights.

So, three problems:

  1. Why doesn’t Nexus search the proxied registries when using the Group?
  2. Why is it saying Unauthorized when using the proxied registries directly through their connector port?
  3. What was the problem I got with the blobstore for the suse proxy repository?
Reply all
Reply to author
Forward
0 new messages