docker从私有镜像库pull/push镜像问题:Error response from daemon: Get https://harbor.op.xxxx.com/v2/: x509: certificate signed by unknown authority

环境centos7+docker 1.17

解决方法:
1. 添加https证书,方法自己搜下
2. 加--insecure-registry参数

配置文件位置
/usr/lib/systemd/system/docker.service
ExecStart=/usr/bin/dockerd --insecure-registry harbor.op.xxxx.com

之前也搜到过ExecStart=/usr/bin/docker daemon -H fd:// --insecure-registry=xxx 这样的写法, docker无法启动,
报错: `docker daemon` is not supported on Linux. Please run `dockerd` directl

加上参数如果启动失败,可以看下日志 See "systemctl status docker.service" and "journalctl -xe" for details.

centos6也是 如此, centos6 + docker 1.7

配置文件位置

/etc/sysconfig/docker
参数加到
other_args

原文地址:http://www.cnblogs.com/yongpan666/p/7890973.html

时间: 2024-10-04 20:33:53

docker从私有镜像库pull/push镜像问题:Error response from daemon: Get https://harbor.op.xxxx.com/v2/: x509: certificate signed by unknown authority的相关文章

mac上docker pull是报错Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable

执行docker pull xx.xx.xx.xx/xx/xx,下载私有库的镜像时报错如下: Error response from daemon: Get https://xx.xx.xx.xx/v2/: Service Unavailable 原因大概是docker默认支持https的协议,而私有库是http的协议. mac桌面可以在Preferences-->Docker Engine里配置以下代码,xx.xx.xx.xx是自己私有库的地址. { "insecure-registri

docker push 出现:x509: certificate signed by unknown authority

今天,部署生产的程序的时候,出现一个问题:编译正常,但是,docker 把编译好的image 推送到生产环境上去的时候,出现:x509: certificate signed by unknown authority 经过上网查找资料得知:是由于证书的错误导致的,但是,并不知道如何解决.后来,解决方案如下: vi /usr/lib/systemd/system/docker.service 添加一列: ExecStart=/usr/bin/dockerd --insecure-registry

docker version:19.03.2 x509: certificate signed by unknown authority

第一步 sudo vim /lib/systemd/system/docker.service 把下面第一行代码替换成第二行(修改“https://127.0.0.1:5000”成私有仓库网址) ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock ExecStart=/usr/bin/dockerd --insecure-registry https://127.0.0.1:5000 -

docker pull / docker login 报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509

docker pull 和 docker login 的时候报错 Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate is valid for bw-production.space, brickworksoftware.com, *.bw-production.space, *.brickworksoftware.com, not registry-1.docker.io 从报错

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

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 headers).See 'docker run --help'. 修改docker镜像源: docke

Docker问题解决:Error response from daemon: Get https://registry-1.docker.io/v2/yandex/clickhouse-server/manifests/latest: net/http: TLS handshake timeout

方法1: vi /etc/docker/daemon.json { "registry-mirrors": ["http://hub-mirror.c.163.com"] } systemctl restart docker.service 方法2: vi /etc/sysconfig/docker OPTIONS='--selinux-enabled --log-driver=journald --registry-mirror=https://docker.mi

使用docker报错 :Error response from daemon: Get https://index.docker.io/v1/search?q=java&n=25: dial tcp:

查看服务器DNS网络配置 vim /etc/resolv.conf 把里面的内容注释,并改为: nameserver 8.8.8.8 nameserver 8.8.8.4 重启网络服务 systemctl restart network 即可 原文地址:https://www.cnblogs.com/zhengyuanyuan/p/11830308.html

Docker获取镜像报错docker: Error response from daemon

docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled今天在使用docker获取镜像时,出现了镜像获取报错的问题,找到了解决的方法记一下. 一.问题 ? ~ docker search sameersbnError response from daemon: Get https://index.docker.io/v1/search?q=sameers

docker export import后,导入镜像,启动时的错误,Error response from daemon: No command specified

Docker的流行与它对容器的易分享和易移植密不可分,用户不仅可以把容器提交到公共服务器上,还可以把容器导出到本地文件系统中.同样,我们也可以把导出的容器重新导入到Docker运行环境中.Docker的容器导入导出分别用import和export命令完成. 1.导出容器export 注意:export导出的是容器,不是镜像. [plain] view plain copy docker export <CONTAINER ID > > my_container.tar docker ex