Registry /docker/distribution v2.2.1Īfter I restart the docker daemon in debug mode, the daemon logs when reproducing my problem are listed below:ĭEBU Calling POST /v1.24/images/create?fromImage=10.10.10.40%3A5000%2Fcadvisor&tag=latestĭEBU hostDir: /etc/docker/certs.d/10.10.10.40:5000ĭEBU Trying to pull 10.10.10.40:5000/cadvisor from v2 WARNING: bridge-nf-call-ip6tables is disabled WARNING: bridge-nf-call-iptables is disabled Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata Use '-storage-opt dm.thinpooldev' to specify a custom block storage device. WARNING: Usage of loopback devices is strongly discouraged for production use.
![docker insecure registry comma docker insecure registry comma](https://docs.docker.com.xy2401.com/v17.09/docker-for-windows/images/proxies.png)
Status: Downloaded newer image for myip:5000/cadvisor:latestĪs suggested by RichardScothern, some relative informations are listed below:ĭata loop file: /var/lib/docker/devicemapper/devicemapper/data Trying to pull repository myip:5000/cadvisor. When I change back docker to 1.10.3, it still work well as below: OPTIONS='-selinux-enabled=true -insecure-registry myip:5000'īut when I exec pull/push,I got this error:Įrror response from daemon: Get http: server gave HTTP response to HTTPS client I had modified the /etc/sysconfig/docker as:
![docker insecure registry comma docker insecure registry comma](https://image.slidesharecdn.com/sonatypenexusdockerregistry-170309140242/95/sonatype-nexus-docker-registry-29-638.jpg)
![docker insecure registry comma docker insecure registry comma](https://i1.wp.com/nikhilwanpal.in/wp-content/uploads/2018/01/cropped-NW-siteicon.png)
My private registry worked well based on docker 1.10.3, but it can't pull/push images after docker updated to 1.12.0.