Running origin as a container, I cannot create new app #7256
Comments
|
Try setting HTTPS_PROXY and HTTP_PROXY on your openshift container as env vars (-e to docker) |
|
@smarterclayton thought you said those env vars will have no effect on new-app? isn't the issue here that new-app is attempting to make a direct connection to the registry and it's not going through a proxy to do so? |
|
@rualthan note that --allow-missing-images actually should get you past this, since it will allow new-app to ignore the fact that it couldn't find the image in the registry. As long as your openshift env itself (and docker daemon) have the right proxy configuration, it should ultimately succeed, though it's a bad way to have to run since new-app is supposed to be able to query registries so it can help you find the right image to use. |
|
Those env vars need to be on the server, not on the client in order to work On Fri, Feb 12, 2016 at 12:23 PM, Ben Parees notifications@github.com
|
|
@smarterclayton yeah sorry was thinking we were in the old direct registry lookup path. makes sense, thanks. |
|
@smarterclayton Sorry I am not sure I understand what needs to be done. In the container, I have done This is the part I didn't get "as env vars (-e to docker)". |
|
After setting the env vars oc new-app --allow-missing-images openshift/deployment-exampleerror: can't look up Docker image "openshift/deployment-example": Internal error occurred: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection |
|
@rualthan you need to pass a -e argument to your docker run command when you start the openshift master image. the -e arguments you need to pass should set the HTTP_PROXY and HTTPS_PROXY values (case sensitive). you should also pull a new image as we've fixed a couple issues around new-app and this behavior. |
|
@bparees @smarterclayton That works. Thank you. For the benefit of others(newbies) here is my Docker run command I also tried export HTTP_PROXY and HTTPS_PROXY (in upper case). In both cases, they showed up in env output. What is the difference between exporting env vars inside container and passing it to the Docker run command? |
|
exporting env vars inside the container won't affect the process that's already started within the container. |
I am trying OO on a RHEL Atomic Host. I spun up OO master as a container following this guide
https://docs.openshift.org/latest/getting_started/administrators.html
After attaching a shell to the Master Container, I cannot deploy an app following the "Try it out" steps
https://docs.openshift.org/latest/getting_started/administrators.html#try-it-out
--allow-missing-images can be used to point to an image that does not exist yet.
See 'oc new-app -h' for examples.
The Atomic host needs proxy to access Internet. I have configured proxy in /etc/sysconfig/docker and that is how I could pull the origin image in the same place.
I am using the image pushed 3 hours ago
oc version
oc v1.1.2-223-g2ca50e6
kubernetes v1.2.0-origin
The text was updated successfully, but these errors were encountered: