docker registry api

悦码客

已于 2022-11-19 00:40:15 修改

阅读量905

点赞数

分类专栏： docker 文章标签： docker

于 2022-11-19 00:38:50 首次发布

本文链接：https://blog.csdn.net/LeMark2333/article/details/127931861

版权

本文介绍了如何使用Docker Registry API删除镜像，包括启用删除API、获取tag引用、通过digest删除和执行garbage collector。还提到了在Registry v2.3及以后版本中必须使用digest进行删除，并提供了批量删除脚本和Linux查找命令的提示。

摘要由CSDN通过智能技术生成

remove registry

https://stackoverflow.com/questions/43666910/remove-docker-repository-on-remote-docker-registry

enable DELETE API:
1. by config.yml : storage.delete.enabled:true
2. by env: -e REGISTRY_STORAGE_DELETE_ENABLED=true
get the tag reference via GET /v2//manifests/ (don’t forget to have Header Accept: application/vnd.docker.distribution.manifest.v2+json).

in response headers, you have docker-content-digest: sha256:xxx

send DELETE /v2//manifests/sha256:xxx
run garbage collector: bin/registry garbage-collect /etc/docker/registry/config.yml
remove files: rm -r /var/lib/registry/docker/registry/v2/repositories//

registry api


DELETE /v2/<name>/manifests/<reference>

/v2/python/manifests/

/v2/quay.io/coreos/flannel/manifests/

https://docker-hub.one-k.xyz/v2/quay.io/coreos/flannel/tags/list


https://docker-hub.one-k.xyz/v2/openstack.kolla/ubuntu-source-mariadb-clustercheck/manifests/wallaby

https://docker-hub.one-k.xyz/v2/openstack.kolla/ubuntu-source-mariadb-clustercheck/manifests/sha256:d9992cc4f3edd222c9871dac91fbdd3cb4cf47570f0038e4574781df77808eed


c0cd30b832e6

registry api


GET	/v2/<name>/tags/list	Tags	Fetch the tags under the repository identified by name.
GET	/v2/<name>/manifests/<reference>	Manifest	Fetch the manifest identified by name and reference where reference can be a tag or digest. A HEAD request can also be issued to this endpoint to obtain resource information without receiving all data.

和我们 free_cicd 业务场景也没啥任何冲突，这边主要针对 gpu 企业生产，单子都是 100w 以上的，我们搞好之后想卖 10w 以下的普通办公还有家庭共享高档 pc

test delete by http

Deleting an Image
An image may be deleted from the registry via its name and reference. A delete may be issued with the following request format:

DELETE /v2//manifests/
For deletes, reference must be a digest or the delete will fail. If the image exists and has been successfully deleted, the following response will be issued:

202 Accepted
Content-Length: None
If the image had already been deleted or did not exist, a 404 Not Found response will be issued instead.

Note When deleting a manifest from a registry version 2.3 or later, the following header must be used when HEAD or GET-ing the manifest to obtain the correct digest to delete:

简单讲就是 version 2.3 or later,
必须根据 digest 才可以删除 image