Browse code

Updated troubleshooting guide with information about insecure-registry

Maciej Szulik authored on 2015/11/24 23:59:32
Showing 1 changed files
... ...
@@ -99,6 +99,23 @@ If it's not running, you can launch it via:
99 99
 
100 100
     $ oadm registry --create --credentials="${KUBECONFIG}"
101 101
 
102
+Insecure Docker Registry
103
+------------------------
104
+
105
+If you have problems when pushing to integrated registry, for example following failures in build logs:
106
+
107
+    E1124 14:51:23.828346       1 dockerutil.go:74] push for image 172.30.216.184:5000/test/image:latest failed, will retry in 5s seconds ...
108
+    ...
109
+    F1124 14:51:28.828654       1 builder.go:60] Build error: Failed to push image. Response from registry is: unable to ping registry endpoint https://172.30.216.184:5000/v0/
110
+    v2 ping attempt failed with error: Get https://172.30.216.184:5000/v2/: tls: oversized record received with length 20527
111
+     v1 ping attempt failed with error: Get https://172.30.216.184:5000/v1/_ping: tls: oversized record received with length 20527
112
+
113
+If you are running Docker as a service via `systemd`, add the `--insecure-registry 172.30.0.0/16` argument to the options value in `/etc/sysconfig/docker` and restart the Docker daemon.  Otherwise, add "--insecure-registry 172.30.0.0/16" to the Docker daemon invocation, eg:
114
+
115
+        $ docker daemon --insecure-registry 172.30.0.0/16
116
+
117
+The value of your network might differ, consult OpenShift master configuration (`master-config.yaml`) for `networkConfig.serviceNetworkCIDR` value.
118
+
102 119
 Probing Containers
103 120
 ------------------
104 121