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

Re: oc cluster up from master doesn't pull image from docker hub first time.





On Wed, Mar 28, 2018 at 4:56 PM, Michal Fojtik <mfojtik redhat com> wrote:
Out of curiosity, is this on OSX?

The image pull issue was fixed here:
https://github.com/openshift/origin/pull/19040

The PR is still waiting in the queue.


Tried with this PR and looks like some regression now :(

```
$ ./oc cluster up
Pulling image openshift/origin:v3.10
Pulled 1/4 layers, 26% complete
Pulled 1/4 layers, 52% complete
Pulled 2/4 layers, 69% complete
Pulled 3/4 layers, 86% complete
Pulled 3/4 layers, 95% complete
Pulled 3/4 layers, 100% complete
Pulled 4/4 layers, 100% complete
Extracting
Image pull complete
Starting OpenShift using openshift/origin:v3.10 ...
I0328 17:50:04.164369   48840 config.go:45] Running "create-node-config"
Error: error creating node config: could not run "create-node-config": Docker run error rc=1

$ git log --pretty=format:"%h - %an, %ar : %s"
ca8bd346fc - Praveen Kumar, 19 minutes ago : Merge branch 'fix-oc-cluster-up' of https://github.com/derekwaynecarr/origin into derekwaynecarr
3619023895 - OpenShift Merge Robot, 2 hours ago : Merge pull request #19116 from rajatchopra/ovn_dind
96c26534e2 - Rajat Chopra, 16 hours ago : cluster cidr format has changed: fix it for ovn-dind
bd17376547 - OpenShift Merge Robot, 20 hours ago : Merge pull request #19102 from bparees/custom_binary
```
 

On 28 March 2018 at 13:02:35, Praveen Kumar
(kumarpraveen nitdgp gmail com) wrote:
> Hi,
>
> Today I built origin repo locally and tried to play around with `oc cluster
> up`. Following is what I observe and not sure if this is an issue or
> something intentional.
>
> ```
> $ ./oc version
> oc v3.10.0-alpha.0+3619023-386
> kubernetes v1.9.1+a0ce1bc657
> features: Basic-Auth
>
> Server https://127.0.0.1:8443
> openshift v3.10.0-alpha.0+efea9a0-380
> kubernetes v1.9.1+a0ce1bc657
>
> $ ./oc cluster up => This should automatic pull the image from docker hub
> after search locally instead failling.
> error: FAIL
> Error: cannot create volume share
> Caused By:
> Error: cannot create container using image openshift/origin:v3.10
> Caused By:
> Error: Error: No such image: openshift/origin:v3.10
>
> $ docker pull openshift/origin:v3.10
> v3.10: Pulling from openshift/origin
> 5e35d10a3eba: Pull complete
> 93c60e8488b9: Pull complete
> 941517f80b9e: Pull complete
> ff7a659ebc1c: Pull complete
> Digest:
> sha256:0039d203d6ee636da95e253b764292362af7e0e6f1d1705b97e4c22933025bb2
> Status: Downloaded newer image for openshift/origin:v3.10
>
> $ ./oc cluster up
> Starting OpenShift using openshift/origin:v3.10 ...
> I0328 16:17:13.343170 42477 config.go:38] Running "create-master-config"
> I0328 16:17:16.452841 42477 config.go:45] Running "create-node-config"
> [...]
> The server is accessible via web console at:
> https://127.0.0.1:8443
>
> You are logged in as:
> User: developer
> Password:
>
> To login as administrator:
> oc login -u system:admin
>
> WARNING: An HTTP proxy (docker.for.mac.http.internal:3128) is configured
> for the Docker daemon, but you did not specify one for cluster up
> WARNING: An HTTPS proxy (docker.for.mac.http.internal:3129) is configured
> for the Docker daemon, but you did not specify one for cluster up
> WARNING: A proxy is configured for Docker, however 172.30.1.1 is not
> included in its NO_PROXY list.
> 172.30.1.1 needs to be included in the Docker daemon's NO_PROXY
> environment variable so pushes to the local OpenShift registry can succeed.
> ```
>
>
>
> --
> Praveen Kumar
> http://fedoraproject.org/wiki/User:Kumarpraveen
> http://fedoraproject.org/
> http://kumar-pravin.blogspot.com
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>



--

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