I think there might be a little confusion here. I'm not using a proxy
between the master and the pods, the proxy is only for getting access to
the Internet. My understanding is that nodes running the pods would need
access to the Internet to download images from the docker hub, and to
install
*Generally*, a proxy shouldn't be between the router or master servers and
the pods themselves. So in production I would expect you to not have that
issue because you should be able to identify your masters via hostname or
long term IP (and thus be able to put them in NO_PROXY). Running in a
Thanks for that info.
Your suggestion for #2 worked perfectly, I'll open a bug as you suggest.
As for #3, it turns out it's all down to being behind a web proxy. I was
only setting the upper case versions of the HTTP_PROXY, HTTPS_PROXY and
NO_PROXY env vars, which curl was not picking up. The
The first problem is probably because the request hadn't completely
finished to import the image. We should report a better error / wait for
the import to happen. Please open a bug describing what you did and we'll
try to give you a better experience.
For #2 - clean up what you did before, and
Hi,
I've just started looking at OpenShift Origin. I'm attempting to get it
going on a CentOS Atomic Host box, and I've been following the Getting
Started guide at https://docs.openshift.org/latest/getting_started/
administrators.html#getting-started-administrators, using the method to run
origin
