推送到不同的 nexus 存储库总是落入一个 repo
Pushing into different nexus repository always lands into one repo
我正在尝试将图像推送到 nexsus 存储库 (myrepo)：
docker push myreposerver/myrepo/httpd:2.4.28-alpine
我看到它出现在另一个仓库中，如下所示：
myreposerver/otherrepo/myrepo/httpd:2.4.28-alpine
这是错误的，但我在 Nexus 中找不到导致此行为的配置设置在哪里 UI。
https://help.sonatype.com/display/NXRM3/Private+Registry+for+Docker
The docker client does not allow a context as part of the path to a
registry, as the namespace and image name are embedded in the URLs it
uses. This is why requests to repositories on the repository manager
are served on a specific and separate port from the rest of the
application instead of how most other repositories serve content via a
path i.e. //
因此，简而言之，如果要在 Nexus 中设置单独的 Docker 存储库，它们必须位于单独的端口上，完全按照此处所述：http://www.sonatype.org/nexus/2017/02/16/using-nexus-3-as-your-repository-part-3-docker-images/
我正在尝试将图像推送到 nexsus 存储库 (myrepo)：
docker push myreposerver/myrepo/httpd:2.4.28-alpine
我看到它出现在另一个仓库中，如下所示：
myreposerver/otherrepo/myrepo/httpd:2.4.28-alpine
这是错误的，但我在 Nexus 中找不到导致此行为的配置设置在哪里 UI。
https://help.sonatype.com/display/NXRM3/Private+Registry+for+Docker
The docker client does not allow a context as part of the path to a registry, as the namespace and image name are embedded in the URLs it uses. This is why requests to repositories on the repository manager are served on a specific and separate port from the rest of the application instead of how most other repositories serve content via a path i.e. //
因此，简而言之，如果要在 Nexus 中设置单独的 Docker 存储库，它们必须位于单独的端口上，完全按照此处所述：http://www.sonatype.org/nexus/2017/02/16/using-nexus-3-as-your-repository-part-3-docker-images/