docker 解决 x509: certificate signed by unknown authority

最新推荐文章于 2025-10-10 15:55:18 发布

原创最新推荐文章于 2025-10-10 15:55:18 发布 · 1.8w 阅读

1 ·

CC 4.0 BY-SA版权

docker 专栏收录该内容

8 篇文章

订阅专栏

博客提及服务器版本为17.09.1 - ce，这是信息技术领域中关于服务器版本的关键信息。

# vim /etc/docker/daemon.json
{ 
  "insecure-registries": ["registry.svc.xxx.cn"]
}
#systemctl restart docker

Server Version: 17.09.1-ce

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

zimu312500

关注关注

3
点赞
踩
1

收藏

觉得还不错? 一键收藏
2
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

专栏目录

Tanzu:x509: certificate signed by unknown authority

随笔记录-分享&记忆

06-24

911

x509: certificate signed by unknown authority ERRO[0000] Error occurred during HTTP request: Get https://192.16.6.1/wcp/loginbanner: x509: certificate signed by unknown authority There was an error when trying to connect to the server 解决办法：如果出于任何原因无法添加证书

【云原生技术】K8s 在拉取镜像时报错tls: failed to verify certificate: x509: certificate signed by unknown authority

weixin_46453070的博客

07-04

2187

原因 Kubernetes 节点在拉取镜像时会对 Harbor 的 HTTPS 证书做严格校验；日志里的核心报错是： ``` tls: failed to verify certificate: x509: certificate signed by unknown authority ``` 说明 Harbor 返回的服务器证书要么是自签发，要么缺少在系统信任链里的根/中级 CA，节点因此拒绝连接。你需要让 **所有负责拉镜像的节点（containerd 或 Docker 守护进程）

2 条评论您还未登录，请先登录后发表或查看评论

containerd拉取私有仓库镜像报错x509: certificate signed by unknown authority

邢宁

04-13

1万+

报错原因分析私有仓库使用的是harbor，由于harbor连接默认需要https认证，crictl拉取镜像默认不带证书访问，所以会报错解决 #下载证书并放到指定目录，证书如何下载看下图 mkdir /etc/containerd/core.harbor.domain cp ca.crt /etc/containerd/core.harbor.domain/ 修改containerd配置文件 vim /etc/containerd/config.toml #配置endpoint连接地址 [p

go get x509:certificate signed by unknown authority

qq_38189542的博客

03-14

2980

在arm设备上构建golang 1.22的Docker镜像，用来做程序的编译镜像，直接安装用ubuntu作为基础镜像，构建好的镜像，在编译的时候执行go get的时候，会报下面错误。

wsl上使用docker pull私有仓库报错x509 certificate signed by unknown authority，解决方法

最新发布

weixin_46007266的博客

10-10

184

因为安装在 Windows 上的 docker 桌面是在 Windows 文件系统上查找证书，而不是在 WSL2 上的 Linux 文件系统上查找证书证书。然后参照其他教程，在docker配置加入insecure-registries，或者在wsl添加相应证书即可。停用 wsl 集成设置（取消勾选）

x509: certificate signed by unknown authority；容器部署的服务建立https通信报错

qq_37106501的博客

11-30

4181

x509: certificate signed by unknown authority docker-compose部署的服务访问https报错

x509: certificate signed by unknown authority (possibly because of “crypto/rsa: verification error“

johnhuster的专栏

10-29

7717

执行下面命令初始化k8s集群时 kubeadm init --pod-network-cidr 10.21.0.0/16 \ --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers 通过 kubectl get pods -n kube-system 查看pods状态发现coredns对应的pod状态为ContainerCreating，通过kubectl describe pods -n kube-

解决docker 推送自签证书仓库报错：403 forbidden或者x509: certificate signed by unknown authority错误

jiaohuizhuang6019的博客

11-16

2663

解决docker 推送自签证书仓库报错：403 forbidden或者x509: certificate signed by unknown authority错误

container向harbor推送镜像报错 x509: certificate signed by unknown authority

平庸

08-28

403

摘要：本文记录了解决Harbor镜像推送认证问题的过程。首先下载新域名证书并配置到containerd指定位置，通过openssl验证证书链有效性。确认证书正确后，将CA证书复制到系统信任目录并更新证书缓存。随后清理containerd缓存并重启服务，最终使用ctr命令成功推送镜像。整个过程涉及证书验证、系统证书配置和containerd服务管理等关键步骤。

golang 报错 `tls: failed to verify certificate: x509: certificate signed by unknown authority`

JineD的博客

11-28

1503

报错的位置是 golang 的 http client，并未有很特殊的配置。

Docker 从 Openshift 内部 Registry 拉镜像遇到 x509: certificate signed by unknown authority 错误的解决方案

weixin_52344179的博客

03-17

1091

环境 Openshift 4.6 问题 Docker 从 Openshift 内部 Registry 拉镜像遇到 x509: certificate signed by unknown authority 错误 docker pull default-route-openshift-image-registry.apps.lab.example.com/ibm-spectrum-scale-ns/scale-gui:5.1.0.1 Trying to pull default-route-openshif

docker login : x509: certificate signed by unknown authority

张伯毅的专栏

08-29

2761

docker login 登录harbor镜像仓库报错.

x509: certificate signed by unknown authority （golang http请求报错）

D1124615130的博客

04-14

2733

client初始化时加上t.TLSClientConfig = &tls.Config{InsecureSkipVerify: true}

Harbor/Docker: x509: certificate signed by unknown authority

热门推荐

tom_fans的博客

07-27

2万+

完成Harbor安装之后，我们使用docker login/push/pull去与Harbor打交道，上传下载镜像等。但是发现出现x509: certificate signed by unknown authority之类的错误。 [root@test01 harbor.dev]# docker login harbor.dev Authenticating with existing credentials... Login did not succeed, error: Error respon

x509: certificate signed by unknow n authority

ic_xcc的博客

09-08

5058

最近的go项目遇见这个问题，记录一下，问题起因是调用别的项目组接口时，接口由http更改为https，之前调试通过的调用接口推送信息方式返回的request请求报错如下：x509: certificate signed by unknow n authority 几番查找之后修改完毕，更改如下 1.引入 "crypto/tls" 包 2.定义TLSClientConfig，忽略证书校验原写法 //发起请求 func Request(url string, header http.Header,

docker 报错x509: certificate signed by unknown authority

Python开发分享的博客

12-14

1万+

1.未开启证书验证的仓库 # vim /etc/docker/daemon.json { "insecure-registries": ["registry.svc.xxx.cn"] } #systemctl restart docker 2.开启证书验证的仓库从私有仓库拉取镜像时报错： docker pull x509:certificate signed by unknown authority 解决方案： 1、登陆私有仓库服务器，进入/etc/docker/certs.d/目录

Get “https://xx.xx.x.xx/v2/“: x509: certificate signed by unknown authority

qq_1801743621的博客

06-26

1559

Get "https://xx.xx.x.xx/v2/": x509: certificate signed by unknown authority

docker buildx 构建多平台镜像错误x509: certificate signed by unknown authority

三劫散仙

05-30

2742

buildx 构建时，如果去公司内部的仓库拉取镜像时，会遇到下面的这种授权不通过问题。添加到BuildKitd容器中。

x509: certificate signed by unknown authority (harbor)

xiunai78的专栏

03-19

2万+