Delete Image Tags in the Docker Registry

Added uuid for "delete-image-tags-in-the-docker-registry-8e2e91d42294"
Updated Patchset 3 comments
Updated Patchset 2 comments
Updated Patchset 1 comments
https://github.com/distribution/distribution/issues/1566

Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: Ic2f00dfb6f906a8cdb1c94dfec565a0b875edea7
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
This commit is contained in:
Juanita-Balaraj 2021-09-27 16:06:28 -04:00
parent 02bb1768b4
commit c2aa4a8764
2 changed files with 31 additions and 0 deletions

View File

@ -0,0 +1,29 @@
.. _delete-image-tags-in-the-docker-registry-8e2e91d42294:
========================================
Delete Image Tags in the Docker Registry
========================================
When deleting image tags in the registry.local docker registry, you should be
aware that the deletion of an **<image-name><tag-name>** will delete all tags
under the specified <image-name> that have the same 'digest' as the specified
<image-name:tag-name>.
The docker registry API v2 does not support deleting specific tags.
See, `https://github.com/distribution/distribution/issues/1566 <https://github.com/distribution/distribution/issues/1566>`_ .
For example:
jsmith/sampleimage-test:v1.0
jsmith/sampleimage-test:v1.1
jsmith/sampleimage-production:v1.0
If the above three image tags share the same digest in registry.local, then, if
'jsmith/sampleimage-test:v1.1' is deleted, then **ALL** other tags under
'jsmith/sampleimage-test' that have the **SAME** digest
(as jsmith/sampleimage-test:v1.1) are deleted. That is, both
'jsmith/sampleimage-test:v1.0' and 'jsmith/sampleimage-test:v1.1' will be
deleted, while 'jsmith/sampleimage-production:v1.0' with the same digest
but different <image-name> will not be deleted.

View File

@ -67,6 +67,8 @@ Local Docker registry
kubernetes-user-tutorials-authentication-and-authorization
using-an-image-from-the-local-docker-registry-in-a-container-spec
delete-image-tags-in-the-docker-registry-8e2e91d42294
---------------------------
NodePort usage restrictions