更新docker到1.12后无法拉/推图像

Question

私有注册表基于docker 1.10.3运行良好，但在docker更新为1.12.0后我无法拉/推图像。

我已将/ etc / sysconfig / docker修改为：

OPTIONS='--selinux-enabled=true --insecure-registry=myip:5000'

或

OPTIONS='--selinux-enabled=true --insecure-registry myip:5000'

但是当我执行pull / push时，我收到了这个错误：

$ docker pull myip:5000/cadvisor
Using default tag: latest
Error response from daemon: Get https://myip:5000/v1/_ping: http: server gave HTTP response to HTTPS client

当我将docker更改为1.10.3时，它仍然可以正常工作，如下所示：

$ docker pull myip:5000/cadvisor
Using default tag: latest
Trying to pull repository myip:5000/cadvisor ... 
latest: Pulling from myip:5000/cadvisor
09d0220f4043: Pull complete 
a3ed95caeb02: Pull complete 
151807d34af9: Pull complete 
14cd28dce332: Pull complete     
Digest:
sha256:33b6475cd5b7646b3748097af1224de3eee3ba7cf5105524d95c0cf135f59b47
Status: Downloaded newer image for myip/cadvisor:latest

下面列出了一些相关信息：

docker version
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built:

OS/Arch: linux/amd64

Server:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built:

OS/Arch: linux/amd64

docker info
Containers: 4
Running: 1
Paused: 0
Stopped: 3
Images: 241
Server Version: 1.12.0
Storage Driver: devicemapper
Pool Name: docker-253:0-6809-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem: xfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 5.459 GB
Data Space Total: 107.4 GB
Data Space Available: 34.74 GB
Metadata Space Used: 9.912 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.138 GB
Thin Pool Minimum Free Space: 10.74 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
WARNING: Usage of loopback devices is strongly discouraged for production use. Use '--storage-opt dm.thinpooldev' to specify a custom block storage device.
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2016-06-09)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: host overlay null bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 3.10.0-229.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 24
Total Memory: 62.39 GiB
Name: server_3
ID: TITS:BL4B:M5FE:CIRO:5SW6:TVIV:HW36:J7OS:WLHF:46T6:2RBA:WCNV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 21
Goroutines: 32
System Time: 2016-08-02T10:33:06.414048675+08:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
127.0.0.0/8

docker exec <registry-container> registry -version
registry github.com/docker/distribution v2.2.1

在调试模式下重新启动docker守护程序后，下面列出了重现我的问题时守护程序日志：

DEBU[0794] Calling POST /v1.24/images/create?fromImage=10.10.10.40%3A5000%2Fcadvisor&tag=latest 
DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000 
DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000 
DEBU[0794] Trying to pull 10.10.10.40:5000/cadvisor from https://10.10.10.40:5000 v2 
WARN[0794] Error getting v2 registry: Get https://10.10.10.40:5000/v2/: http: server gave HTTP response to HTTPS client 
ERRO[0794] Attempting next endpoint for pull after error: Get https://10.10.10.40:5000/v2/: http: server gave HTTP response to HTTPS client
DEBU[0794] Trying to pull 10.10.10.40:5000/cadvisor from https://10.10.10.40:5000 v1 
DEBU[0794] hostDir: /etc/docker/certs.d/10.10.10.40:5000
DEBU[0794] attempting v1 ping for registry endpoint https://10.10.10.40:5000/v1/
DEBU[0794] Fallback from error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client 
ERRO[0794] Attempting next endpoint for pull after error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client
ERRO[0794] Handler for POST /v1.24/images/create returned error: Get https://10.10.10.40:5000/v1/_ping: http: server gave HTTP response to HTTPS client 
DEBU[1201] clean 2 unused exec commands

更重要的是，我只是运行一个简单的命令来启动私有注册表以进行测试，其他任何东西都是默认的：

docker run -d -p 5000:5000 --restart=always --name registry -v 'pwd'/data:/var/lib/registry registry:2

未配置代理。总之，它只是一个安静的测试环境。

Answer 1

我遇到了同样的问题。

这对我有帮助：

• 在客户端计算机上创建或修改 /etc/docker/daemon.json

  { "insecure-registries":["myregistry.example.com:5000"] }

• 重启docker守护程序

  sudo /etc/init.d/docker restart

Answer 2

对于Windows用户

在此处添加本地注册表并申请：

Answer 3

如果您使用的是Windows，则会出现此错误，您需要在此处创建一个文件："C:\ProgramData\docker\config\daemon.json"

和上面提到的@Bspec一样：

{＆＃34; insecure-registries＆＃34;：[＆＃34; myregistry.example.com：5000＆＃34;]}

然后使用PowerShell命令重新启动docker：

Stop-Service docker
Start-Service docker

Answer 4

对于Mac用户： 使用顶部栏中的（docker）图标更新docker偏好设置

首选项->守护程序->不安全的注册表[单击（+）符号]->添加：port

点击底部的“应用并重新启动”按钮

Answer 5

我也遇到了同样的问题，并遵循以下步骤：

1。创建文件

 vi /etc/docker/daemon.json

2。添加以下内容

{
        "insecure-registries":["192.168.1.142:5000"]
 }

3。重新启动Docker

service docker restart

Answer 6

为了进行推送，请将IP添加到客户端的不安全注册表中（例如，对于Windows）

要拉，请将其添加到服务器端（在本例中为Ubuntu）

vim /etc/docker/daemon.json

，然后重新启动Docker。

Answer 7

修改“ /etc/docker/daemon.json”对我不起作用。

按如下所示将其放入“ / etc / sysconfig / docker”下，即可。

INSECURE_REGISTRY =“-不安全的注册表192.168.24.1:8787”

Answer 8

所有解决方案都无法在Ubuntu 18.04上运行，因此请花一些时间来查找根本原因。

解决问题的步骤

sudo vi /lib/systemd/system/docker.service
# ExecStart=dockerd .... --insecure-registry=192.168.99.100:5000
sudo systemctl stop docker.service
sudo systemctl daemon-reload
sudo systemctl start docker.service

---

出了什么问题？

无论使用哪种Linux发行版，我都建议检查dockerd选项的确切配置位置。

sudo find /etc /lib -name 'docker*' | while read -r line; do grep dockerd $line /dev/null; done