Details
Description
Related to this specific reproduce are possibly these issues:
NEXUS-24124
NEXUS-24485
NEXUS-25626
When we retag and push an image into Nexus using podman cli
but the same steps work absolutely fine if we use docker cli.
Given a Hosted Docker repo with Deployment Policy Allow Once...and allowing latest tag redeployment is allowed, then
For example, Below will FAIL
# After pushing anomaly-detection:latest into a docker-hosted repo podman pull registry.example.com/anomaly-detection:latest # This tag 10-27-2020 is new and does not exist in the docker-hosted repo yet podman tag registry.example.com/anomaly-detection:latest example.net/dcp/dcp/anomaly-detection:10-27-2020 podman push example.net/dcp/dcp/anomaly-detection:10-27-2020
But using the same with docker cli (below) would succeed
docker pull registry.example.com/anomaly-detection:latest docker tag registry.example.com/anomaly-detection:latest example.net/dcp/dcp/anomaly-detection:10-27-2020 docker push example.net/dcp/dcp/anomaly-detection:10-27-2020
Attachments
Issue Links
- is related to
-
NEXUS-24124 OCI - Docker repos should respect accept headers
-
- Closed
-
-
NEXUS-24485 Docker Manifest generation is incorrect for Redeploy Disabled repositories.
-
- Closed
-
-
NEXUS-25626 Docker redeploy on the latest tag fails when more than one tag exists for the image
-
- Closed
-