x509: certificate signed by unknown authority harbor 架构图
Posted littlevigra
tags:
篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了x509: certificate signed by unknown authority harbor 架构图相关的知识,希望对你有一定的参考价值。
默认时,client 与 Registry 的交互是通过 https 通信的。在 install Registry 时,若未配置任何tls 相关的 key 和 crt 文件,https 访问必然失败。使用 "--insecure-registry <harbor IP>"
可以指定 client 与 Registry 以 http 的方式进行通信。
重载、重启 docker 服务,验证配置是否生效
1
2
3
4
5
6
7
8
|
[root@c7-QHost ~]# systemctl daemon-reload
[root@c7-QHost ~]# systemctl restart docker
[root@c7-QHost ~]# docker info
...
Insecure Registries:
172.16.0.11
127.0.0.0/8
|
[root@node239 ~]# docker pull 10.1.1.50/myproject/mywordpress:v1
v1: Pulling from myproject/mywordpress
c20dc0c5afeb: Pull complete
5190cd8121fb: Pull complete
9bdc26132342: Pull complete
87783d526d1f: Pull complete
04 - Docker 私有仓库 | Mallux - 宁静致远
https://blog.mallux.me/2017/03/15/harbor/ --- 参考文档
以上是关于x509: certificate signed by unknown authority harbor 架构图的主要内容,如果未能解决你的问题,请参考以下文章
x509: certificate signed by unknown authority harbor 架构图
docker version:19.03.2 x509: certificate signed by unknown authority
Error response from daemon: Get https: x509: certificate signed by unknown authority
.NET 中的 X509Certificate2 和 X509Certificate 有啥区别?
Bouncycastle:X509CertificateHolder 到 X509Certificate?
X509Chain.Build(...) System.InvalidCastException 从 X509Certificate 到 X509Certificate2