私人註冊表是基於泊塢窗1.10.3效果不錯，但我不能拉/泊塢窗更新至1.12.0後推的圖像。不能推/拉更新泊塢窗後的圖像，以1.12

我已經修改了的/ etc/SYSCONFIG /泊塢窗爲：

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

或

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

但是當我exec的推/拉，我得到這個錯誤：

$ 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

當我搬運工變回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

我重新啓動在調試模式下的泊塢窗守護程序後，重現我的問題時，守護進程會記錄如下：

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

未配置代理。總之，它只是一個安靜的測試環境。

來源

2016-08-01 yuxiaoyu

好，我也面臨同樣的錯誤，但奇怪的是我沒有/ etc/sysconfig/docker文件在RHEL 7中，你k現在我可以找到任何類似的文件？這個docker文件的內容是什麼？謝謝。 – sai

如果您想更改docker守護程序的運行方式，則此文件包含一些選項。我不知道RHEL7中的確切路徑。但是如果使用命令「$ sudo locate docker」執行命令，則會在某處找到該文件 – yuxiaoyu

我最終刪除了/etc/docker/daemon.json並重新啓動了docker服務，它看起來像是覆蓋了/ etc/sysconfig/docker中設置的內容 –

110

我有同樣的問題。

這幫助我：

創建或在客戶機上修改/etc/docker/daemon.json

{ "insecure-registries":["myregistry.example.com:5000"] }
重啓碼頭工人守護

sudo /etc/init.d/docker restart

來源

2016-08-02 09:13:01 bojtib

它對我也有幫助！非常感謝你！但是，原因是什麼？ – yuxiaoyu

在我的情況下，我使用Ubuntu 16.04和/ etc/default/docker（我的配置是）特定於暴發戶。 16.04使用systemd。 /etc/docker/daemon.json是平臺無關的配置。 https://github.com/docker/docker/issues/23512 https://github.com/docker/docker/issues/23228 – bojtib

這裏是文檔如何設置不安全的註冊表 https：//docs.docker。 com/registry/insecure/ –

如果您使用的是Windows，你會得到這個錯誤，你需要在這裏創建一個文件："C:\ProgramData\docker\config\daemon.json"

，做同樣的@Bspec上面提到的：

{「不安全 - 登記」：「myregistry.example。COM：

Stop-Service docker 
Start-Service docker

來源

2017-03-02 11:54:48

對於Windows用戶

添加本地註冊表這裏和應用：5000" ]}

使用PowerShell命令，然後重啓泊塢窗

來源

2017-09-11 12:56:34 kogoia

不能推/拉更新泊塢窗後的圖像，以1.12

回答

這幫助我：

相關問題