0

Docker version 20.10.8, build 3967b7dCentOS-7.9主机Sonatype Nexus Repository Manager version - OSS 3.30.1-01上使用并用作私有 docker 注册表。当我尝试使用它提取图像时,docker-compose它总是失败并出现以下错误。

$ docker-compose up -d
Pulling prometheus (internal-registry.com:8335/prometheus:latest)...
ERROR: manifest for internal-registry.com:8335/prometheus:latest not found: manifest unknown: manifest unknown

错误Sonatype Nexus server log如下。

2021-10-11 10:35:41,307+0530 WARN  [qtp657241891-125]  admin org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: HEAD /v2/library/prometheus/manifests/latest: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: authentication required
2021-10-11 10:35:42,106+0530 WARN  [qtp657241891-560]  admin org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/library/prometheus/manifests/latest: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: authentication required.

Docker 主机docker login to our private registry成功。

1) Repo - Allow clients to use the V1 API to interact with this repository (Tick mark enabled).
2) DockerHub(Proxy) - Allow clients to use the V1 API to interact with this repository (Tick mark enabled).
3) Group - Allow clients to use the V1 API to interact with this repository (Tick mark enabled).

4) Nexus UI > Security > Anonymous Access > Allow anonymous users to access the server - (Tick mark enabled).
Username: anonymous
Realm: Local Autherizing Realm

5) Nexus UI > Security > Role > Create role > Create Nexus role > Created new role
Privileges: nx-repository-view-*-*-*-broswe
            nx-repository-view-*-*-*-read
Roles: Contained - nx-anonymous

6) Nexus UI > Security > Users > anonymous(Active)
         Roles: Granted: read_and-browse

7) Nexus UI > Security > Realms - Docker Bearer Token Realm (Is in Active List) 

not found: manifest unknown: manifest unknown拉取 docker 镜像时仍然出错。我该如何解决这个问题?任何指针都会有所帮助。谢谢!

4

2 回答 2

0

这看起来像是某种网络/内存/硬件问题,可能在 internal-registry.com 上,假设 prometheus 是该注册表上的可用映像。我将首先对该服务进行负载测试,然后验证 dns,然后是防火墙,然后是内存,然后是电源,然后是该服务的硬件以对其进行故障排除。

最后,我将尝试在另一个环境中重新创建此错误,再次针对 internal-registry.com。如果不能,那么问题出在 docker 客户端上,但我怀疑您将能够在其他客户端上复制此问题。

于 2021-10-10T03:52:51.750 回答
0
  1. 确保泊坞窗图像(上面是错误的)。

  2. 链接有助于在 Nuxus 端的存储库上创建一个Read&特权。Browse发布能够成功拉取图像的帖子。

于 2021-10-12T07:51:32.887 回答