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

Re: Pushing Image Fails



I'm guessing you created the registry, deleted it at some point, and then recreated it. You need to restart the master if you do that (we're working on eliminating this issue, but it's going to take some time).

Andy

On Wed, Jul 22, 2015 at 2:24 PM, Dean Peterson <peterson dean gmail com> wrote:

I get the following error while trying to build with the sample application-template-stibuild.json

"dockerutil.go:50] push for image 172.30.75.223:5000/test/origin-ruby-sample failed, will retry in 10s ...
F0722 17:05:56.719020 1 builder.go:70] Build error: Failed to push image: API error (500): v1 ping attempt failed with error: Get http://172.30.75.223:5000/v1/_ping: read tcp 172.30.75.223:5000: connection reset by peer"

My private registry gives me this information when I run ./oc describe service docker-registry:

Name: docker-registry
Labels: docker-registry=default
Selector: docker-registry=default
Type: ClusterIP
IP: 172.30.168.237
Port: 5000/TCP
Endpoints: 172.17.0.11:5000
Session Affinity: None
No events.

Where is the ip address: 172.30.75.223:5000 coming from in the build logs when trying to push the image. Shouldn't that address be 172.30.168.237:5000?


_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



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