docker部署harbor踩坑记录Error response from daemon: Get https://192.168.102.73/v2/: x509:certificate signe

限时加码!20+主流AI编程工具免费用 购周边加赠Coding Plan Lite,Claude Code、Cursor等即刻畅享,学习进阶更高效! 阅读详情

docker  login报错1:

客户端登录:
[root@client ~]# docker login -u admin -p harbor123456 192.168.102.73
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://192.168.31.10/v2/: x509: certificate signed by unknown authority
  
以上出现报错,解决办法:
此种情况多发生在自签名的证书,报错含义是签发证书机构未经认证,无法识别。
 
解决办法(要替换自己证书的路径目录):
[root@localhost harbor]# chmod 644 /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
[root@localhost harbor]# cat /etc/docker/cert/192.168.102.73.crt >> /etc/pki/tls/certs/ca-bundle.crt
[root@localhost harbor]# chmod 444 /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
 
由于证书是docker的daemon需要用到的,所以需要重启docker服务,进而也要重启docker-compose
[root@localhost harbor]# systemctl daemon-reload
[root@localhost harbor]# systemctl restart docker
[root@localhost harbor]# docker-compose down -v
Stopping harbor-log ... done
Removing nginx             ... done
Removing harbor-jobservice ... done
Removing harbor-core       ... done
Removing harbor-portal     ... done
Removing redis             ... done
Removing registry          ... done
Removing registryctl       ... done
Removing harbor-db         ... done
Removing harbor-log        ... done
Removing network harbor_harbor
[root@localhost harbor]# docker-compose up -d
Creating network "harbor_harbor" with the default driver
Creating harbor-log ... done
Creating registry      ... done
Creating registryctl   ... done
Creating harbor-db     ... done
Creating harbor-portal ... done
Creating redis         ... done
Creating harbor-core   ... done
Creating harbor-jobservice ... done
Creating nginx             ... done
 
然后再次尝试在harbor本机登陆, 发现就可以正常登陆了!!
[root@localhost harbor]# docker login -u admin -p harbor123456 192.168.102.73
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded

参考原文链接:https://blog.csdn.net/youmatterhsp/article/details/105868624

                        

docker  login报错2:

[root@k8s-node3 harbor]# docker login -u admin -p Harbor12345 192.168.102.73 
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get "https://192.168.102.73/v2/": Get "https://harbor.mes.com:8082/service/token?account=admin&client_id=docker&offline_token=true&service=harbor-registry": dial tcp 192.168.102.73:8082: connect: connection refused


解决办法:
vim harbor.yml 
# external_url: https://harbor.mes.com:8082 #注释相关配置

#因创建私有证书时未设置相关域名直接使用的IP配置

docker拉取镜像时报错:docker: Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp: 错误信息:docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 192.168.100.2:53: server misbehaving. 阅读详情

相关推荐

Error response from daemon: Gethttps://harbor.com/v2/“: x509: certificate relies on legacy Common

1、先到harbor服务上查看 docker-compose服务是否正常,2、 修改客户端docker 相关配置文件。

weixin_44130953的博客 3488

【错误】Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp: lookup registry-1.

今天准备搭建一下ELK集群,结果第一步下载镜像时就除了问题,这也是用Docker依赖第一次遇到问题,报错如下: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on 8.8.8.8:53: read udp 192.168.241.128:34634->8.8.8.8:53: i/o timeout 8.8.8.8设置为DNS服

weixin_47255175的博客 6万+

Error response from daemon Get server gave HTTP response to HTTPS client

使用docker compose拉起docker镜像时,若出现如下报错表示Docker守护进程无法从指定url获取响应,

null 4713

【已解决】Error response from daemon: Gethttps://registry-1.docker.io/v2/“: net/http: request canceled

【已解决】Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.xxx.xxx:xx: read udp 192.168.xxx.xxx:xxxxx->192.168.xxx.xxx:xx: read: connection refused

weixin_43608968的博客 3万+

解决docker拉取镜像时报错Error response from daemon: Get ““: http: server gave HTTP response to HTTPS client

1.编辑docker中的daemon.json文件,没有就创建。例如镜像仓库地址:192.168.1.111:5000。场景:新搭建一台服务器,需要拉取公司私有镜像仓库。2.在文件中添加如下内容。3. 重新加载daemon。4.重启docker

h_and_g的博客 5591

解决Error response from daemon: Gethttps://registry-1.docker.io/v2/“: read: connection refused问题

在用docker容器下载rabbitmq时出现报错如下 Error response from daemon: Gethttps://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:50086->[::1]:53: read: connection refused 因为之前用docker下载过redis,mysql,nginx都没出现过问题,这次下载消息队列中间

KevinForeverquit的博客 3万+

【异常解决】(二)解决docker报错Error response from daemon: Get... http: server gave HTTP response to HTTPS

解决docker报错:Error response from daemon: Get "...": http: server gave HTTP response to HTTPS client

foolishsunday的博客 1万+

Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp [2600:1f18:2148:bc01:57

执行 ==docker pull mysql:8.0.30==命令报错:Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc01:571f:e759:a87a:2961]:443: connect: network is unreachable

严同学在努力 3万+

Docker报错Error response from daemon: Get

因为Docker的底层是基于Linux的,所以需要到控制面板-->程序-->启动或关闭Windows功能。问题1:没配置国内镜像导致的连接不稳地(阿里云镜像只能用在阿里云的服务器,本地也不行)2024年10月14起,阿里云镜像仅限在阿里云产品上使用了,所以你在本地使用也不行。问题2:在Windows环境下,没开启Linux的服务支持。第三个问题我没遇到,前两个是我遇到解决了的。把下面两个勾选上,然后要重启才能生效。问题3:保护进程IPv6报错。

m0_62097957的博客 4714

Docker pull拉取镜像报错“Error response from daemon: Gethttps://registry-1.docker.io/v2”解决办法

Docker pull拉取镜像报错“Error response from daemon: Get "https://registry-1.docker.io/v2”解决办法

jks212454的博客 7万+

解决docker: Error response from daemon: Gethttps://registry-1.docker.io/v2/“:连接超时问题

最近在温习Docker安装MySQL时,出现了以下问题。注意:由于之前创建过目录,因此这个命令。: 以下解决方式,来自于黑马教程。没有创建的不能跳过。:听网友说是阿里加速镜像。之前安装Docke时,

y2020520的博客 3万+

解决docker拉取镜像报错:Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp

今天做完一个新项目,搭建了一个新的虚拟机,打算使用docker来搭建各种环境,发现拉取镜像报错。一看,挺新奇,一开始只是简单的以为我打错命令了,以为docker没有这个镜像,然后查询下mysql镜像:

weixin_47316183的博客 17万+

解决Error response from daemon: Get https://: http: server gave HTTP response to HTTPS client

背景:在一台服务器上,拉取私有镜像仓库中的镜像报错; 镜像仓库地址:192.168.1.26:5000 报错信息如下: ErrImagePull: rpc error: code = Unknown desc = Error response from daemon: Get https://192.168.1.26:5000/v2/: http: server gave HTTP response to HTTPS client 解决方式: 1. 编辑docker dae...

SerryYang的博客 5万+

docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled

sudo docker run hello-world docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting h...

BigData_Mining的博客 9万+

docker拉取镜像报错:Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp的解决过程例子解析

在使用Docker拉取镜像时遇到“Error response from daemon: Gethttps://registry-1.docker.io/v2/“: dial tcp”这样的错误,通常意味着Docker客户端尝试连接到Docker Hub的镜像仓库时出现了网络连接问题。如果以上步骤都不能解决问题,可以考虑查看Docker官方文档或者社区论坛获取更多帮助。同时,确保你的系统时间和日期是准确的,因为时间同步问题有时也会导致连接错误。

IT老农民的博客 3万+

解决Error response from daemon: Get**问题

Error response from daemon: Get** 后面是no such host或者Temporary failure in name resolution

qq_53689523的博客 5819

彻底解决Error response from daemon: Gethttps://registry-1.docker.io/v2/“: net/http: request cancele 报错

亲测有效,上配置!!!!!!!亲测有效,上配置!!!!!!!

Hey!的博客 7793

docker 报错Error response from daemon: Get https:///v1 proxyconnect tcp: dial tcp 127.0.0.1

删除代理的内容,把http-proxy.conf里面的内容注释掉。1.修改daemon.json,往里面增加地址。原因一: docker使用了代理。3、刷新docker配置。4、重启docker2.重启docker

xiaoyaozizai1的博客 4867

【解决】Error response from daemon: Get "https://xxx.xx.xx.xxx/v2/": x509: certificate signed by unknown...

【解决】Error response from daemon: Get "https://xxx.xx.xx.xxx/v2/": x509: certificate signed by unknown authority ...

SummerGao 6290
上一篇: 国产服务器KyLinV10操作系统部署harbor仓库时报错:open /etc/registry/passwd: permission denied
小角色也有大梦想
博客等级 码龄9年 66粉丝 18原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值