简体繁体 English

允许在 Nexus OSS 中重新部署“最新”的 docker 标签

[英]Allow redeploy for “latest” docker tag in Nexus OSS

原文 2017-03-20 15:41:12 5 2 docker/ nexus

I'm using nexus to host both maven and docker artifacts.我正在使用 nexus 来托管 maven 和 docker 工件。 For the docker production artifacts I'd like to turn on "disable redeploy" to ensure the image can never change on the nexus server once it is potentially in production.对于 docker 生产工件，我想打开“禁用重新部署”以确保映像一旦可能投入生产就永远不会在 nexus 服务器上更改。

However, enabling "disable redeploy" appears to make it impossible to re-publish the "latest" tag to point to the latest version.但是，启用“禁用重新部署”似乎无法重新发布“最新”标签以指向最新版本。

When trying to push I get obscure errors on the client such as blob upload invalid: blob upload invalid .尝试推送时，我在客户端上遇到模糊错误，例如blob upload invalid: blob upload invalid 。

Is it possible to disable redeploy to concrete version tags, while allowing on tags like "latest"是否可以禁用重新部署到具体版本标签，同时允许使用“最新”等标签

2 个解决方案

In sonartype version 3.21.1 this feature has been added.在 sonartype 版本 3.21.1 中添加了此功能。 When the Disable redeploy policy is selected , we get new option: Allow redeploying the 'latest' tag but defer to the Deployment Policy for all other tags.选择禁用REDEPLOY策略时，我们获取新选项：允许重新部署“最新”标记，但将推迟到所有其他标记的部署策略。

Link: https://issues.sonatype.org/browse/NEXUS-18186链接： https : //issues.sonatype.org/browse/NEXUS-18186

This is not possible.这不可能。 It does seem like a bit of an oddity given how the Docker format works.考虑到 Docker 格式的工作原理，这看起来确实有点奇怪。 You can pop over to https://issues.sonatype.org/browse/NEXUS and file an issue about this functionality.您可以跳到https://issues.sonatype.org/browse/NEXUS并提交有关此功能的问题。