多种方法创建docker registry

爱被打了一巴掌 2022-07-14 09:26 166阅读 0赞

搭建[Docker][]私仓，可以使用docker官方提供的[registry][]镜像。该镜像目前有2.0，2.3和2.3.1版本。它只与1.6.0以上版本的docker兼容。搭建私仓的步骤如下：

**一：无代理、无认证的registry**

1：下载registry镜像：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  docker pull registry:2

这里必须加上标签”:2”，否则的话，不加标签的registry，实际上下载的是标签为”latest”的registry镜像，则不能使用下面的nginx代理镜像：containersol/docker-registry-proxy

2：创建registry容器：

在registry:2创建的私有仓库中，上传的镜像保存在容器的/var/lib/registry目录下。创建registry:2的容器时，会自动创建一个数据卷(Data Volumes)，数据卷对应的宿主机下的目录一般为：/var/lib/docker/volumes/XXX/\_data。

可以在创建registry:2的容器时，通过-v参数，修改这种对应关系：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  docker run -d -p 5000:5000 --restart=always –v \\ /opt/docker/registry/data:/var/lib/registry --name docker-registry registry:2

除了可以将数据保存在当前主机的文件系统上，registry也支持其他基于云的存储系统，比如S3，Microsoft Azure, Ceph Rados, OpenStack [Swift][] and Aliyun OSS等。可以在配置文件中进行配置：https://github.com/docker/distribution/blob/master/docs/configuration.md\#storage

以上其实已经创建好了一个docker私有仓库，但是这时候向其push或者pull时还是有问题的：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \[@hh\_93\_197 /\]\# docker tag hello-world 192.168.1.104:5000/hello-world 
2.  \[@hh\_93\_197 /\]\# docker push 192.168.1.104:5000/hello-world 
3.  The push refers to a repository \[192.168.1.104:5000/hello-world\] 
4.  unable to ping registry endpoint https://192.168.1.104:5000/v0/ 
5.  v2 ping attempt failed with error: Get https://192.168.1.104:5000/v2/: tls: oversized record received with length 20527 
6.   v1 ping attempt failed with error: Get https://192.168.1.104:5000/v1/\_ping: tls: oversized record received with length 20527

这是因为从docker1.3.2版本开始，使用registry时，必须使用TLS保证其安全。

### 最简单的解决办法是，在需要连接该私有仓库的所有客户端docker宿主机上，修改docker[daemon][]的配置文件，增加insecure-registry参数。 ###

比如，对于Redhat7的宿主机来说，新增文件/etc/systemd/system/docker.service.d/docker.conf，其内容配置如下：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \[Service\] 
2.  ExecStart= 
3.  ExecStart=/usr/bin/docker daemon -H fd:// --insecure-registry=192.168.1.104:5000

然后，重启docker：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \[root@localhost /\]\# systemctl daemon-reload 
2.  \[root@localhost /\]\# service docker restart

此时就可以使用该私有仓库了。

但是，上面这种配置方式既不安全（所有人都可以push或pull），也很不方便（使用该私有仓库的所有宿主机上都这样进行配置）。

下面是带有认证的registry私仓构建过程：

**二：无代理，有认证的registry**

使用TLS认证registry容器时，必须有证书。一般情况下，是要去认证机构购买签名证书。这里使用openssl生成自签名的证书。

1：生成自签名证书

一般情况下，证书只支持域名访问，要使其支持IP地址访问，需要修改配置文件openssl.cnf。

在Redhat7系统中，文件所在位置是/etc/pki/tls/openssl.cnf。在其中的\[ v3\_ca\]部分，添加subjectAltName选项：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \[ v3\_ca \] 
2.  subjectAltName = IP:192.168.1.104

接下来就是生成自签名的证书：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  mkdir -p /opt/docker/registry/certs 
2.  
3.  openssl req -x509 -days 3650 -nodes -newkey rsa:2048 \\ 
4.  \-keyout /opt/docker/registry/certs/domain.key \\ 
5.  \-out /opt/docker/registry/certs/domain.crt 
6.  ... 
7.  Country Name (2 letter code) \[XX\]: 
8.  State or Province Name (full name) \[\]: 
9.  Locality Name (eg, city) \[Default City\]: 
10. Organization Name (eg, company) \[Default Company Ltd\]: 
11. Organizational Unit Name (eg, section) \[\]: 
12. Common Name (eg, your name or your server's hostname) \[\]:192.168.1.104:5000 
13. Email Address \[\]:

这里的服务器域名写成”192.168.1.104:5000”，后续就使用该地址访问私仓。其余项直接回车即可。

2：创建带有TLS认证的registry容器

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  docker run \\ 
2.  \-d \\ 
3.  \--name docker-registry-no-proxy --restart=always \\ 
4.  \-v /opt/docker/registry/data:/var/lib/registry \\ 
5.  \-u root \\ 
6.  \-p 192.168.1.104:5000:5000 \\ 
7.  \-v /opt/docker/registry/certs:/certs \\ 
8.  \-e REGISTRY\_HTTP\_TLS\_CERTIFICATE=/certs/domain.crt \\ 
9.  \-e REGISTRY\_HTTP\_TLS\_KEY=/certs/domain.key \\ 
10. registry:2

3：配置客户端宿主机

目前，已经搭建好了一个registry私有仓库了。但是，访问该私仓还是会报错：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker pull 192.168.1.104:5000/redis 
2.  Using default tag: latest 
3.  Error response from daemon: unable to ping registry endpoint https://192.168.1.104:5000/v0/ 
4.  v2 ping attempt failed with error: Get https://192.168.1.104:5000/v2/: x509: certificate signed by unknown authority 
5.   v1 ping attempt failed with error: Get https://192.168.1.104:5000/v1/\_ping: x509: certificate signed by unknown authority

这是因为客户端宿主机上没有相应的证书。需要把registry所在主机上，刚生成的证书：

/opt/docker/registry/certs/domain.crt

复制到客户端宿主机上的：

/etc/docker/certs.d/192.168.1.104:5000/ca.crt

之后，就可以使用该私仓了：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker pull 192.168.1.104:5000/redis 
2.  Using default tag: latest 
3.  latest: Pulling from redis 
4.  80ab95908a2b: Pull complete 
5.  a3ed95caeb02: Pull complete 
6.  47a0d79f89b9: Pull complete 
7.  7190081b1686: Pull complete 
8.  fe09c22d81ac: Pull complete 
9.  a5eae2bcc645: Pull complete 
10. 662723161f77: Pull complete 
11. b568670a8ccd: Pull complete 
12. a1a961e320bc: Pull complete 
13. Digest: sha256:769ac80a4711258ec4d6d325f3ad31fbce3bbfa006d5f8aae94c94917dfb0384 
14. Status: Downloaded newer image for 192.168.1.104:5000/redis:latest

更好的方式是使用nginx代理，由nginx提供https的ssl的认证和basicauthentication。方法如下：

**三：nginx代理，域名访问的registry**

1：生成自签名证书：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  mkdir -p /opt/docker/registry/conf 
2.  openssl req -x509 -days 3650 -nodes -newkey rsa:2048 \\ 
3.  \-keyout /opt/docker/registry/conf/docker-registry.key \\ 
4.  \-out /opt/docker/registry/conf/docker-registry.crt 
5.  
6.  ... 
7.  Country Name (2 letter code) \[XX\]: 
8.  State or Province Name (full name) \[\]: 
9.  Locality Name (eg, city) \[Default City\]: 
10. Organization Name (eg, company) \[Default Company Ltd\]: 
11. Organizational Unit Name (eg, section) \[\]: 
12. Common Name (eg, your name or your server's hostname) \[\]:hh.registry.com 
13. Email Address \[\]:

这里的服务器域名写成”hh.registry.com”，其余项直接回车即可。

2：创建能够访问仓库的用户名和密码

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  htpasswd -b -c -d /opt/docker/registry/conf/docker-registry.htpasswd admin admin

这里的用户名和密码都是admin

3：运行nginx

这里使用容器containersol/docker-registry-proxy运行nginx：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  docker run -d \\ 
2.  \-p 443:443 \\ 
3.  \--name docker-registry-proxy \\ 
4.  \-e REGISTRY\_HOST="docker-registry" \\ 
5.  \-e REGISTRY\_PORT="5000" \\ 
6.  \-e SERVER\_NAME="hh.registry.com" \\ 
7.  \--link docker-registry:docker-registry \\ 
8.  \-v /opt/docker/registry/conf/docker-registry.htpasswd:/etc/nginx/.htpasswd:ro \\ 
9.  \-v /opt/docker/registry/conf:/etc/nginx/ssl:ro \\ 
10. containersol/docker-registry-proxy

注意，这里的环境变量SERVER\_NAME也要设置成”hh.registry.com”.

目前，就已经搭建好了一个registry私有仓库了。但是，还需要在使用它的客户端宿主机执行以下的操作。比如在私有仓库所在的主机上使用它，也要执行以下步骤：

4：修改/etc/hosts文件，增加以下内容，以使客户端宿主机可以解析域名”hh.registry.com”

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  192.168.1.104 hh.registry.com

5：复制证书

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  mkdir -p /etc/docker/certs.d/hh.registry.com 
2.  cp /opt/docker/registry/conf/docker-registry.crt /etc/docker/certs.d/hh.registry.com/ca.crt

这里是在registry所在主机上进行的操作。如果是其他docker宿主机，需要远程复制该crt文件。

客户端宿主机配置好以后，通过下面的方式验证私有仓库的可用性：

6：列出私有仓库上的所有镜像

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \#curl -X GET https://admin:admin@hh.registry.com/v2/\_catalog -k 
2.  \{"repositories":\["hello-world","ubuntu"\]\}

7：登陆

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \#docker login -u admin -p admin -e a hh.registry.com 
2.  WARNING: login credentials saved in /root/.docker/config.json 
3.  Login Succeeded

8：pull镜像

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \#docker pull hh.registry.com/ubuntu 
2.  Using default tag: latest 
3.  latest: Pulling from ubuntu 
4.  5a132a7e7af1: Pull complete 
5.  fd2731e4c50c: Pull complete 
6.  28a2f68d1120: Pull complete 
7.  a3ed95caeb02: Pull complete 
8.  Digest: sha256:9409f5e54fdc68ef3f0aae3c5ffac22bfe2aabd0b363a4bdbe5292c93b75a661 
9.  Status: Downloaded newer image for hh.registry.com/ubuntu:latest

9：push镜像

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker tag registry.aliyuncs.com/ddbmh/redis hh.registry.com/redis 
2.  \# docker push hh.registry.com/redis 
3.  The push refers to a repository \[hh.registry.com/redis\] 
4.  5f70bf18a086: Mounted from ubuntu 
5.  7986f971c50f: Pushed 
6.  590d3336f33c: Pushed 
7.  4458b6e6f424: Pushed 
8.  39d2b75cc73d: Pushed 
9.  cbc6c973b349: Pushed 
10. d53a2702e023: Pushed 
11. 5bca8d976dd8: Pushed 
12. 603fd967d41c: Pushed 
13. latest: digest: sha256:769ac80a4711258ec4d6d325f3ad31fbce3bbfa006d5f8aae94c94917dfb0384 size: 3823

10：再次列出私有仓库中的所有镜像

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# curl -X GET https://admin:admin@hh.registry.com/v2/\_catalog -k 
2.  \{"repositories":\["hello-world","redis","ubuntu"\]\}

**四：nginx代理，IP访问的registry**

以上的步骤中，访问私仓只能使用域名”hh.registry.com”，如果使用IP访问，则会报错：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \#docker login -u admin -p admin -e a 192.168.1.104 
2.  Error response from daemon: invalid registry endpoint https://192.168.1.104/v0/: unable to ping registry endpoint https://192.168.1.104/v0/ 
3.  v2 ping attempt failed with error: Get https://192.168.1.104/v2/: x509: cannot validate certificate for 192.168.1.104 because it doesn't contain any IP SANs 
4.  ...

如果想用IP地址访问，则执行以下的步骤：

1：在文件/etc/pki/tls/openssl.cnf的\[ v3\_ca \]部分，添加subjectAltName选项

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \[ v3\_ca \] 
2.  subjectAltName = IP:192.168.1.104

2：重新生成证书

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  openssl req -x509 -days 3650 -nodes -newkey rsa:2048 \\ 
2.  \-keyout /opt/docker/registry/conf\_ip/docker-registry.key \\ 
3.  \-out /opt/docker/registry/conf\_ip/docker-registry.crt 
4.  
5.  ... 
6.  Country Name (2 letter code) \[XX\]: 
7.  State or Province Name (full name) \[\]: 
8.  Locality Name (eg, city) \[Default City\]: 
9.  Organization Name (eg, company) \[Default Company Ltd\]: 
10. Organizational Unit Name (eg, section) \[\]: 
11. Common Name (eg, your name or your server's hostname) \[\]:hh.registry.com 
12. Email Address \[\]:

这里的服务器域名还是写成”hh.registry.com”即可。其余项直接回车即可。

3：创建能够访问仓库的用户名和密码

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  htpasswd -b -c -d /opt/docker/registry/conf\_ip/docker-registry.htpasswd admin admin

这里的用户名和密码都是admin

4：运行nginx容器

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker stop docker-registry-proxy 
2.  docker-registry-proxy 
3.  
4.  \# docker run -d \\ 
5.  \-p 443:443 \\ 
6.  \--name docker-registry-proxy-ip \\ 
7.  \-e REGISTRY\_HOST="docker-registry" \\ 
8.  \-e REGISTRY\_PORT="5000" \\ 
9.  \-e SERVER\_NAME="hh.registry.com" \\ 
10. \--link docker-registry:docker-registry \\ 
11. \-v /opt/docker/registry/conf\_ip/docker-registry.htpasswd:/etc/nginx/.htpasswd:ro \\ 
12. \-v /opt/docker/registry/conf\_ip:/etc/nginx/ssl:ro \\ 
13. containersol/docker-registry-proxy

搭建好registry私有仓库后，在需要访问该私仓的客户端docker宿主机上，无需修改/etc/hosts文件，直接将registry主机上的证书，复制成客户端docker宿主机上的/etc/docker/certs.d/192.168.1.104/ca.crt文件。

客户端docker宿主机配置好以后，验证步骤如下：

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# curl -X GET https://admin:admin@192.168.1.104/v2/\_catalog -k 
2.  \{"repositories":\["hello-world","redis","ubuntu"\]\}

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker login -u admin -p admin -e a 192.168.1.104 
2.  WARNING: login credentials saved in /root/.docker/config.json 
3.  Login Succeeded

**\[plain\]** [view plain][] [copy][view plain]

[![在CODE上查看代码片][CODE]][CODE_CODE] [![派生到我的代码片][ico_fork.svg]][ico_fork.svg 1]

1.  \# docker pull 192.168.1.104/redis 
2.  Using default tag: latest 
3.  latest: Pulling from redis 
4.  80ab95908a2b: Pull complete 
5.  a3ed95caeb02: Pull complete 
6.  47a0d79f89b9: Pull complete 
7.  7190081b1686: Pull complete 
8.  fe09c22d81ac: Pull complete 
9.  a5eae2bcc645: Pull complete 
10. 662723161f77: Pull complete 
11. b568670a8ccd: Pull complete 
12. a1a961e320bc: Pull complete 
13. Digest: sha256:769ac80a4711258ec4d6d325f3ad31fbce3bbfa006d5f8aae94c94917dfb0384 
14. Status: Downloaded newer image for 192.168.1.104/redis:latest

参考：

https://docs.docker.com/registry/

https://hub.docker.com/r/chalimartines/cdh5-pseudo-distributed/

http://www.pangxie.space/docker/353

https://docs.docker.com/registry/insecure/

http://www.tianmaying.com/tutorial/docker-registry

[Docker]: http://lib.csdn.net/base/docker
[registry]: https://hub.docker.com/r/_/registry/
[view plain]: http://blog.csdn.net/gqtcgq/article/details/51163558#
[CODE]: https://code.csdn.net/assets/CODE_ico.png
[CODE_CODE]: https://code.csdn.net/snippets/1648841
[ico_fork.svg]: https://code.csdn.net/assets/ico_fork.svg
[ico_fork.svg 1]: https://code.csdn.net/snippets/1648841/fork
[Swift]: http://lib.csdn.net/base/swift
[daemon]: http://www.baidu.com/link?url=gScz1rMO4qA2ttFptWJ98MtBd-aKyijatbLKyY1QngF2Z_K22A-XdFLagohuekZnnv_4aA8xcOoCyL43bF5lQq