[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: oc new-app says "network is unreachable" when using images from the registry - but telnet works

Am 2016-04-05 um 17:53 schrieb Ben Parees:

On Tue, Apr 5, 2016 at 11:44 AM, v <vekt0r7 gmx net> wrote:


we have upgraded to OS 1.1.4 and we are getting the following error message when using oc new-app to start an app which uses an image from our registry:

oc new-app
error: can't look up Docker image "": Internal error occurred: Get dial tcp network is unreachable
error: no match for ""

Howerver, the following things work:
-oc new-app with an image from docker.io
-pushing to the registry (docker login, docker push)
-telnet 5000 works from all nodes

This is a very weird error because telnet works. And the error only started appearing after the upgrade. Any help would be highly appreciated.

​do you have any http_proxy/https_proxy env variables configured?



users mailing list
users lists openshift redhat com

Ben Parees | OpenShift


We thought of that possibility too. But we don't use a proxy:
ps -eF | grep docker
root        6503       1 10 1767802 153628 1 13:15 ?       00:29:32 /usr/bin/docker daemon --insecure-registry= --selinux-enabled --log-level=warn --storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/docker--vg-docker--pool --storage-opt dm.use_deferred_removal=true -b=lbr0 --mtu=1450

Is there any other place where http_proxy/https_proxy env variables could be configured other than in the global docker daemon settings? Or anything else which could cause that?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]