在前边的博客中我们说到docker的架构由docker客户端、服务端以及仓库组成；docker仓库就是用来存放镜像的地方；其实docker registry我们理解为存放docker镜像仓库的仓库比较准确吧；因为docker的镜像仓库通常是把同一类的镜像用不同的版本来区别，而registry则是用来存放这些仓库的仓库；默认安装docker都是从dockerhub镜像仓库下载镜像；其实在生产环境中，我们很少去公有仓库上下载镜像，原因之一是公有仓库中的镜像在生产环境中使用，有些不适配，通常我们是去公有仓库下载基础镜像，然后基于基础镜像构建适合自己生产环境中的镜像；其次公有仓库镜像有很多都不是安全的镜像，这么说吧，我们不确定自己下载的镜像是否有后门，是否有挖矿代码，所以基于种种因素，我们还是有必要搭建自己私有的镜像仓库；今天我们就来聊一聊docker的私有镜像仓库的搭建；
1、查看docker-distribution包简介
?| 12345678910111213141516171819 |
[root@docker_registry ~]# yum info docker-distributionLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile * base: mirrors.aliyun.com * extras: mirrors.aliyun.com * updates: mirrors.aliyun.comAvailable PackagesName : docker-distributionArch : x86_64Version : 2.6.2Release : 2.git48294d9.el7Size : 3.5 MRepo : extras/7/x86_64Summary : Docker toolset to pack, ship, store, and deliver contentURL : https://github.com/docker/distributionLicense : ASL 2.0Description : Docker toolset to pack, ship, store, and deliver content [root@docker_registry ~]#
|
提示：docker-distribution这个包就是提供简单仓库服务软件实现；
2、安装docker-distribution
?| 1234567891011121314151617181920212223242526272829303132333435363738394041 |
[root@docker_registry ~]# yum install -y docker-distributionLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile * base: mirrors.aliyun.com * extras: mirrors.aliyun.com * updates: mirrors.aliyun.comResolving DependenciesThere are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction --cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help).The program yum-complete-transaction is found in the yum-utils package.--> Running transaction check---> Package docker-distribution.x86_64 0:2.6.2-2.git48294d9.el7 will be installed--> Finished Dependency Resolution Dependencies Resolved =================================================================================================================== Package Arch Version Repository Size===================================================================================================================Installing: docker-distribution x86_64 2.6.2-2.git48294d9.el7 extras 3.5 M Transaction Summary===================================================================================================================Install 1 Package Total download size: 3.5 MInstalled size: 12 MDownloading packages:docker-distribution-2.6.2-2.git48294d9.el7.x86_64.rpm | 3.5 MB 00:00:03 Running transaction checkRunning transaction testTransaction test succeededRunning transaction Installing : docker-distribution-2.6.2-2.git48294d9.el7.x86_64 1/1 Verifying : docker-distribution-2.6.2-2.git48294d9.el7.x86_64 1/1 Installed: docker-distribution.x86_64 0:2.6.2-2.git48294d9.el7 Complete![root@docker_registry ~]#
|
3、查看docker-distribution安装了那些文件
?| 123456789101112 |
[root@docker_registry ~]# rpm -ql docker-distribution/etc/docker-distribution/registry/config.yml/usr/bin/registry/usr/lib/systemd/system/docker-distribution.service/usr/share/doc/docker-distribution-2.6.2/usr/share/doc/docker-distribution-2.6.2/AUTHORS/usr/share/doc/docker-distribution-2.6.2/CONTRIBUTING.md/usr/share/doc/docker-distribution-2.6.2/LICENSE/usr/share/doc/docker-distribution-2.6.2/MAINTAINERS/usr/share/doc/docker-distribution-2.6.2/README.md/var/lib/registry[root@docker_registry ~]#
|
提示：/etc/docker-distribution/registry/config.yml这个文件用于配置registry的配置文件；/usr/bin/registry是二进制应用程序；/usr/lib/systemd/system/docker-distribution.service 这个文件是docker-distribution的unit file；/var/lib/registry这个目录用于存放我们上传到registry上的镜像存放地；
4、查看配置文件
?| 12345678910111213 |
[root@docker_registry ~]# cat /etc/docker-distribution/registry/config.ymlversion: 0.1log: fields: service: registrystorage: cache: layerinfo: inmemory filesystem: rootdirectory: /var/lib/registryhttp: addr: :5000[root@docker_registry ~]#
|
提示：这个配置文件是一个yml语法的配置文件，从上面的信息可以看到，默认情况docker-distribution监听在tcp的5000端口；存放镜像的目录是/var/lib/registry/目录下；
5、启动docker-distribution
?| 123456789 |
[root@docker_registry ~]# systemctl start docker-distribution[root@docker_registry ~]# ss -tnlState Recv-Q Send-Q Local Address:Port Peer Address:Port LISTEN 0 128 *:22 *:* LISTEN 0 100 127.0.0.1:25 *:* LISTEN 0 128 :::22 :::* LISTEN 0 100 ::1:25 :::* LISTEN 0 128 :::5000 :::* [root@docker_registry ~]#
|
提示：可以看到5000端口已经处于监听状态了；到此docker-distribution就启动起来了；这个仓库服务很简陋，没有用户认证功能，默认是基于http通信而非https，所以从某些角度讲，不是一个安全的仓库；所以一般不见在互联网上使用，在自己的内外环境中可以使用；
这里补充一点，docker的镜像通常是 registry地址加repository名称加版本这三部分组成，registry可以是域名，可以是ip地址加端口，也可以说域名加端口，默认https是443端口，http是80端口，如果不写端口默认是443而非80（原因是docker默认不支持从http协议的仓库下载/上传镜像）；例如 quay.io/coreos/flannel:v0.12.0-s390x 从这个镜像名我们就可以知道registry是https://quay.io;repository名称为coreos/flannel 版本是v0.12.0-s390x;
示例：下载第三方仓库镜像到本地
提示：可以看到下载下来的镜像名称就是我们刚才说的registry+repository+版本；从上面的信息我们可以总结一点，docker镜像的名称（标签）反应了该镜像来自哪个registry的那个仓库；所以我们要下载私有镜像仓库中的镜像就需要把加上私有registry的名称或地址+repository+版本来下载私有镜像仓库中的镜像；同理上传镜像也需要写明上传到那个registry中的那个repository中去；
示例：上传本地镜像到私有仓库
提示：要把本地仓库镜像传到私有仓库中去，首先我们要把本地镜像打一个新的标签，按照我们刚才上面说的逻辑，然后在上传新打到标签的镜像到私有仓库就可以了；从上面的信息我们看到当我们打好标签后，上传镜像时报错了，提示我们仓库不是https的；默认情况docker不支持http明文上传/下载镜像；如果我们非要用http上传下载镜像我们需要在配置文件中明确的告诉docker非安全仓库地址；
配置docker支持私有仓库上传下载镜像
?| 12345678 |
[root@docker_registry ~]# cat /etc/docker/daemon.json{ "registry-mirrors": ["https://registry.docker-cn.com","https://cyr1uljt.mirror.aliyuncs.com"], "insecure-registries": ["192.168.0.99:5000"]} [root@docker_registry ~]# systemctl daemon-reload [root@docker_registry ~]# systemctl restart docker
|
提示：我们通过在配置文件中配置insecure-registries来告诉docker192.168.0.99：5000这个registry是不安全的，但是我们信任这个仓库，大概就是这个意思嘛；通常我们是写主机名然后配合hosts文件来解析的方式来对registry解析；从而把镜像命名为主机名+仓库名+版本的形式；如下所示；这里还需要注意一点insecure-registries后面的列表中的仓库如果有域名，域名不能有下划线（“_”），否则重启docker会起不来；
?| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 |
[root@docker_registry ~]# cat /etc/docker/daemon.json { "registry-mirrors": ["https://registry.docker-cn.com","https://cyr1uljt.mirror.aliyuncs.com"], "insecure-registries": ["192.168.0.99:5000","docker-registry.io:5000"] }[root@docker_registry ~]# cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4::1 localhost localhost.localdomain localhost6 localhost6.localdomain6192.168.0.99 docker-registry.io registry192.168.0.22 docker-node01.io node01192.168.0.23 docker-node02.io node02[root@docker_registry ~]# systemctl restart docker[root@docker_registry ~]# docker infoClient: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 1 Server Version: 19.03.11 Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd init version: fec3683 Security Options: seccomp Profile: default Kernel Version: 3.10.0-693.el7.x86_64 Operating System: CentOS Linux 7 (Core) OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 1.785GiB Name: docker_registry ID: R34V:IG2F:23I6:6WG6:FFQ4:75SV:3UKZ:RFH7:DGCO:QS7V:CS7K:NSH6 Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 192.168.0.99:5000 docker-registry.io:5000 127.0.0.0/8 Registry Mirrors: https://registry.docker-cn.com/ https://cyr1uljt.mirror.aliyuncs.com/ Live Restore Enabled: false [root@docker_registry ~]#
|
提示：重启docker后，如果在docker info 中能够看到我们配置的内容说明配置生效了；现在我们再来传我们新打的标签的镜像，看看是否能够传到我们的私有仓库呢？
?| 1234567891011121314151617181920 |
[root@docker_registry ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEdocker-registry.io:5000/centos 7 b5b4d78bc90c 4 weeks ago 203MBcentos 7 b5b4d78bc90c 4 weeks ago 203MB192.168.0.99:5000/flannel v0.12.0-s390x 57eade024bfb 2 months ago 56.9MBquay.io/coreos/flannel v0.12.0-s390x 57eade024bfb 2 months ago 56.9MB[root@docker_registry ~]# docker push 192.168.0.99:5000/flannel:v0.12.0-s390xThe push refers to repository [192.168.0.99:5000/flannel]b67de7789e55: Pushed 4c4bfa1b47e6: Pushed 3b7ae8a9c323: Pushed fbd88a276dca: Pushed 271ca11ef489: Pushed 1f106b41b4d6: Pushed v0.12.0-s390x: digest: sha256:3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 size: 1579[root@docker_registry ~]# docker push docker-registry.io:5000/centos:7The push refers to repository [docker-registry.io:5000/centos]edf3aa290fb3: Pushed 7: digest: sha256:c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941 size: 529[root@docker_registry ~]#
|
提示：可以看到我们上传的两个镜像都完成了上传没有报错，接下来我们去/var/lib/registry/这个目录，看看是否有这两个镜像相关目录？
?| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596 |
[root@docker_registry ~]# tree /var/lib/registry//var/lib/registry/└── docker └── registry └── v2 ├── blobs │ └── sha256 │ ├── 13 │ │ └── 13b80a37370b57f558a2e06092c39224e5d1ebac50e48df0afdeb43cf2303e60 │ │ └── data │ ├── 17 │ │ └── 176bad61a3a435da03ec603d2bd8f7a69286d92f21f447b17f21f0bc4e085bde │ │ └── data │ ├── 1b │ │ └── 1b56fbc8a8e10830867455c0794a70f5469c154cdc013554daf501aeda3f30fe │ │ └── data │ ├── 26 │ │ └── 266247e2e603e1c840f97cb4d97a08b9184344e9802966cb42c93d21c407839f │ │ └── data │ ├── 3c │ │ └── 3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 │ │ └── data │ ├── 42 │ │ └── 42d8e66fa893de4beb5d136b787cf182b24b7f4972c4212b9493b661ad1d7e85 │ │ └── data │ ├── 52 │ │ └── 524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebc │ │ └── data │ ├── 57 │ │ └── 57eade024bfbd48c45ef2bad996c4d6a0fa41b692247294745265af738066813 │ │ └── data │ ├── 85 │ │ └── 85ecb68de4693bb4093d923f6d1062766e4fa7cbb3bf456a2bc19dd3e6c5e6c6 │ │ └── data │ ├── b5 │ │ └── b5b4d78bc90ccd15806443fb881e35b5ddba924e2f475c1071a38a3094c3081d │ │ └── data │ └── c2 │ └── c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941 │ └── data └── repositories ├── centos │ ├── _layers │ │ └── sha256 │ │ ├── 524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebc │ │ │ └── link │ │ └── b5b4d78bc90ccd15806443fb881e35b5ddba924e2f475c1071a38a3094c3081d │ │ └── link │ ├── _manifests │ │ ├── revisions │ │ │ └── sha256 │ │ │ └── c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941 │ │ │ └── link │ │ └── tags │ │ └── 7 │ │ ├── current │ │ │ └── link │ │ └── index │ │ └── sha256 │ │ └── c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941 │ │ └── link │ └── _uploads └── flannel ├── _layers │ └── sha256 │ ├── 13b80a37370b57f558a2e06092c39224e5d1ebac50e48df0afdeb43cf2303e60 │ │ └── link │ ├── 176bad61a3a435da03ec603d2bd8f7a69286d92f21f447b17f21f0bc4e085bde │ │ └── link │ ├── 1b56fbc8a8e10830867455c0794a70f5469c154cdc013554daf501aeda3f30fe │ │ └── link │ ├── 266247e2e603e1c840f97cb4d97a08b9184344e9802966cb42c93d21c407839f │ │ └── link │ ├── 42d8e66fa893de4beb5d136b787cf182b24b7f4972c4212b9493b661ad1d7e85 │ │ └── link │ ├── 57eade024bfbd48c45ef2bad996c4d6a0fa41b692247294745265af738066813 │ │ └── link │ └── 85ecb68de4693bb4093d923f6d1062766e4fa7cbb3bf456a2bc19dd3e6c5e6c6 │ └── link ├── _manifests │ ├── revisions │ │ └── sha256 │ │ └── 3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 │ │ └── link │ └── tags │ └── v0.12.0-s390x │ ├── current │ │ └── link │ └── index │ └── sha256 │ └── 3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 │ └── link └── _uploads 65 directories, 26 files[root@docker_registry ~]#
|
提示：可以看到对应目录下有两个子目录就是以我们上传的镜像名称命名的；
示例：查看私有仓库中存在的进行列表
?| 123 |
[root@docker_registry ~]# curl docker-registry.io:5000/v2/_catalog{"repositories":["centos","flannel"]}[root@docker_registry ~]#
|
示例：下载私有仓库中的镜像到本地
?| 123456789101112131415161718192021222324252627282930313233343536 |
[root@docker_node01 ~]# ip a l ens332: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:0c:29:22:36:7f brd ff:ff:ff:ff:ff:ff inet 192.168.0.22/24 brd 192.168.0.255 scope global ens33 valid_lft forever preferred_lft forever inet6 fe80::20c:29ff:fe22:367f/64 scope link valid_lft forever preferred_lft forever[root@docker_node01 ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZElinux1874/myimg v0.1 e408b1c6e04f 2 weeks ago 1.22MBwordpress latest c3fa1c8546fb 5 weeks ago 540MBmysql 5.7 f965319e89de 5 weeks ago 448MBalpine v3 f70734b6a266 6 weeks ago 5.61MBnginx 1.14-alpine 8a2fb25a19f5 14 months ago 16MBhttpd 2.4.37-alpine dfd436f9a5d8 17 months ago 91.8MB[root@docker_node01 ~]# docker pull 192.168.0.99:5000/flannel:v0.12.0-s390xv0.12.0-s390x: Pulling from flannel176bad61a3a4: Pull complete 13b80a37370b: Pull complete 42d8e66fa893: Pull complete 266247e2e603: Pull complete 1b56fbc8a8e1: Pull complete 85ecb68de469: Pull complete Digest: sha256:3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6Status: Downloaded newer image for 192.168.0.99:5000/flannel:v0.12.0-s390x192.168.0.99:5000/flannel:v0.12.0-s390x[root@docker_node01 ~]# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZElinux1874/myimg v0.1 e408b1c6e04f 2 weeks ago 1.22MBwordpress latest c3fa1c8546fb 5 weeks ago 540MBmysql 5.7 f965319e89de 5 weeks ago 448MBalpine v3 f70734b6a266 6 weeks ago 5.61MB192.168.0.99:5000/flannel v0.12.0-s390x 57eade024bfb 2 months ago 56.9MBnginx 1.14-alpine 8a2fb25a19f5 14 months ago 16MBhttpd 2.4.37-alpine dfd436f9a5d8 17 months ago 91.8MB[root@docker_node01 ~]#
|
提示：下载私有仓库中的镜像，默认情况docker也是不支持直接访问http协议的仓库，需要我们手动去配置insecure-registries，然后重启docker才可以；
示例：删除私有仓库中的镜像
1、获取对应镜像的sha256的值 curl --header "Accept:application/vnd.docker.distribution.manifest.v2+json" -I -X GET http://<registry addr>/v2/<image name>/manifests/<image tag>
2、删除对应镜像版本元数据 curl -I -X DELETE http://<registry addr>/v2/<image name>/manifests/<image digest>
提示：如果响应405方法不被允许；我们需要修改私有仓库的配置文件，将其配置为允许删除；如下
?| 1234567891011121314151617181920212223 |
[root@docker_registry ~]# cat /etc/docker-distribution/registry/config.ymlversion: 0.1log: fields: service: registrystorage: delete: enabled: true cache: layerinfo: inmemory filesystem: rootdirectory: /var/lib/registryhttp: addr: :5000[root@docker_registry ~]# systemctl restart docker-distribution [root@docker_registry ~]# curl -IX DELETE http://docker-registry.io:5000/v2/centos/manifests/sha256:c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941HTTP/1.1 202 AcceptedDocker-Distribution-Api-Version: registry/2.0Date: Sat, 06 Jun 2020 19:55:52 GMTContent-Length: 0Content-Type: text/plain; charset=utf-8 [root@docker_registry ~]#
|
提示：degest值包含"sha256:"
3、垃圾回收清理
?| 12345678910111213141516171819202122232425262728293031 |
[root@docker_registry ~]# registry garbage-collect /etc/docker-distribution/registry/config.yml centosflannelflannel: marking manifest sha256:3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 flannel: marking blob sha256:57eade024bfbd48c45ef2bad996c4d6a0fa41b692247294745265af738066813flannel: marking blob sha256:176bad61a3a435da03ec603d2bd8f7a69286d92f21f447b17f21f0bc4e085bdeflannel: marking blob sha256:13b80a37370b57f558a2e06092c39224e5d1ebac50e48df0afdeb43cf2303e60flannel: marking blob sha256:42d8e66fa893de4beb5d136b787cf182b24b7f4972c4212b9493b661ad1d7e85flannel: marking blob sha256:266247e2e603e1c840f97cb4d97a08b9184344e9802966cb42c93d21c407839fflannel: marking blob sha256:1b56fbc8a8e10830867455c0794a70f5469c154cdc013554daf501aeda3f30feflannel: marking blob sha256:85ecb68de4693bb4093d923f6d1062766e4fa7cbb3bf456a2bc19dd3e6c5e6c6mywebmyweb: marking manifest sha256:aaf04cf567a776e36eb3b0bafaec17ed8d9e0a743bdb897dca13f251250ae493 myweb: marking blob sha256:4f406abeaab7f848178867409142090d1a551b22b968be6a6dae733c8403738emyweb: marking blob sha256:524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebcmyweb: marking blob sha256:c941076f9075280c41b502283f37ab8bafef3a66f4a7ba299838dce07641a48dtesttest: marking manifest sha256:5ecad23ab8a52e55f93968f708d325261032dd613287aec92e7cf8ddd6426635 test: marking blob sha256:370e3a843c3cb12700301e3f87f929939146cd8b676260bedcd83aaa7fcc2939test: marking blob sha256:524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebctest: marking manifest sha256:da8b53210bf1f4dc4873bbd5589abad616663cda45205ae3a4fffb0729d2730d test: marking blob sha256:461f6ceabc885e2e90b5f9ee82aefc9a30a39510c40e7cd8fb7436a4d340fe1dtest: marking blob sha256:524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebctest: marking blob sha256:035e026f1d6b0acba3413ba616dcbabf75d20e945778c52716e601255452b7b7 17 blobs marked, 2 blobs eligible for deletionblob eligible for deletion: sha256:b5b4d78bc90ccd15806443fb881e35b5ddba924e2f475c1071a38a3094c3081dINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/b5/b5b4d78bc90ccd15806443fb881e35b5ddba924e2f475c1071a38a3094c3081d go.version=go1.9.4 instance.id=b3029d7f-99e8-4941-8c87-989514b584eablob eligible for deletion: sha256:c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941INFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/c2/c2f1d5a9c0a81350fa0ad7e1eee99e379d75fe53823d44b5469eb2eb6092c941 go.version=go1.9.4 instance.id=b3029d7f-99e8-4941-8c87-989514b584ea[root@docker_registry ~]#
|
测试：下载docker-registry.io:5000/centos:7 看看是否还能下载？
?| 123 |
[root@docker_node01 ~]# docker pull 192.168.0.99:5000/centos:7Error response from daemon: manifest for 192.168.0.99:5000/centos:7 not found: manifest unknown: manifest unknown[root@docker_node01 ~]#
|
提示：以上提示告诉我们没有对应镜像的元数据信息；说明我们私有仓库没有对应镜像；以上方法适合精准删除某个镜像的某个版本，如果是删除一个仓库，直接删除 /var/lib/registry/docker/registry/v2/repositories/下对应仓库的目录，然后在用registry命令做垃圾回收；如下
?| 1234567891011121314151617181920212223242526272829303132333435363738394041424344 |
[root@docker_registry ~]# ll /var/lib/registry/docker/registry/v2/repositories/total 0drwxr-xr-x 5 root root 55 Jun 6 14:16 centosdrwxr-xr-x 5 root root 55 Jun 6 14:15 flanneldrwxr-xr-x 5 root root 55 Jun 6 15:25 mywebdrwxr-xr-x 5 root root 55 Jun 6 15:24 test[root@docker_registry ~]# rm -rf /var/lib/registry/docker/registry/v2/repositories/test[root@docker_registry ~]# rm -rf /var/lib/registry/docker/registry/v2/repositories/myweb[root@docker_registry ~]# ll /var/lib/registry/docker/registry/v2/repositories/total 0drwxr-xr-x 5 root root 55 Jun 6 14:16 centosdrwxr-xr-x 5 root root 55 Jun 6 14:15 flannel[root@docker_registry ~]# registry garbage-collect /etc/docker-distribution/registry/config.yml centosflannelflannel: marking manifest sha256:3ce5b8d40451787e1166bf6b207c7834c13f7a0712b46ddbfb591d8b5906bfa6 flannel: marking blob sha256:57eade024bfbd48c45ef2bad996c4d6a0fa41b692247294745265af738066813flannel: marking blob sha256:176bad61a3a435da03ec603d2bd8f7a69286d92f21f447b17f21f0bc4e085bdeflannel: marking blob sha256:13b80a37370b57f558a2e06092c39224e5d1ebac50e48df0afdeb43cf2303e60flannel: marking blob sha256:42d8e66fa893de4beb5d136b787cf182b24b7f4972c4212b9493b661ad1d7e85flannel: marking blob sha256:266247e2e603e1c840f97cb4d97a08b9184344e9802966cb42c93d21c407839fflannel: marking blob sha256:1b56fbc8a8e10830867455c0794a70f5469c154cdc013554daf501aeda3f30feflannel: marking blob sha256:85ecb68de4693bb4093d923f6d1062766e4fa7cbb3bf456a2bc19dd3e6c5e6c6 8 blobs marked, 9 blobs eligible for deletionblob eligible for deletion: sha256:370e3a843c3cb12700301e3f87f929939146cd8b676260bedcd83aaa7fcc2939INFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/37/370e3a843c3cb12700301e3f87f929939146cd8b676260bedcd83aaa7fcc2939 go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebcINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/52/524b0c1e57f8ee5fee01a1decba2f301c324a6513ca3551021264e3aa7341ebc go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:5ecad23ab8a52e55f93968f708d325261032dd613287aec92e7cf8ddd6426635INFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/5e/5ecad23ab8a52e55f93968f708d325261032dd613287aec92e7cf8ddd6426635 go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:aaf04cf567a776e36eb3b0bafaec17ed8d9e0a743bdb897dca13f251250ae493INFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/aa/aaf04cf567a776e36eb3b0bafaec17ed8d9e0a743bdb897dca13f251250ae493 go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:035e026f1d6b0acba3413ba616dcbabf75d20e945778c52716e601255452b7b7INFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/03/035e026f1d6b0acba3413ba616dcbabf75d20e945778c52716e601255452b7b7 go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:461f6ceabc885e2e90b5f9ee82aefc9a30a39510c40e7cd8fb7436a4d340fe1dINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/46/461f6ceabc885e2e90b5f9ee82aefc9a30a39510c40e7cd8fb7436a4d340fe1d go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:4f406abeaab7f848178867409142090d1a551b22b968be6a6dae733c8403738eINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/4f/4f406abeaab7f848178867409142090d1a551b22b968be6a6dae733c8403738e go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:c941076f9075280c41b502283f37ab8bafef3a66f4a7ba299838dce07641a48dINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/c9/c941076f9075280c41b502283f37ab8bafef3a66f4a7ba299838dce07641a48d go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6eblob eligible for deletion: sha256:da8b53210bf1f4dc4873bbd5589abad616663cda45205ae3a4fffb0729d2730dINFO[0000] Deleting blob: /docker/registry/v2/blobs/sha256/da/da8b53210bf1f4dc4873bbd5589abad616663cda45205ae3a4fffb0729d2730d go.version=go1.9.4 instance.id=1a15f1e7-194f-4a82-b79d-9f437d975f6e[root@docker_registry ~]#
|
提示：这种方式比较粗暴简单，通常是一个仓库里只有一个版本镜像可以使用这种方式删除，如果一个仓库有多个版本，那么还是建议使用第一种方式；