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

Re: Unable to pull from registry



I was not able to run two of the commands.  Here are the results of the commands that ran successfully:

 ./oc get -n default se/docker-registry
NAME              LABELS                    SELECTOR                  IP(S)          PORT(S)
docker-registry   docker-registry=default   docker-registry=default   172.30.13.89   5000/TCP
[root localhost openshift]# 

 ./oc status
In project OpenShift 3 Sample (test)

service database (172.30.147.165:5434 -> 3306)
  database deploys docker.io/openshift/mysql-55-centos7:latest 
    #1 deployed 41 hours ago - 1 pod

service frontend (172.30.245.209:5432 -> 8080)
  frontend deploys origin-ruby-sample:latest <-
    builds https://username:password enterprisewebservice kilnhg com/Code/......./ruby-hello-world.git with test/ruby-20-centos7:latest 
    #2 deployment failed 41 hours ago
    #1 deployment failed 41 hours ago

Commands that did not work:

curl -v `./oc get services | grep registry | awk '{print $4":"$5}/v2/' | sed 's,/[^/]\+$,/v2/,'`
curl: no URL specified!
curl: try 'curl --help' or 'curl --manual' for more information

./oc describe pod `./oc get pod | grep docker-registry | awk '{print $1}'`
error: you must provide one or more resources by argument or filename


On Thu, Jul 23, 2015 at 9:54 PM, Nakayama Kenjiro <nakayamakenjiro gmail com> wrote:
Hi,

Could you please show us the following command output?

# curl -v `oc get services | grep registry | awk '{print $4":"$5}/v2/' | sed 's,/[^/]\+$,/v2/,'`
# oc describe service docker-registry
# oc describe pod `oc get pod | grep docker-registry | awk '{print $1}'`
# oc status

*NOTE* Please run them with default project. You can use it with '#oc project default' or 'oc -n default ....'.

Thanks,
Kenjiro


On Fri, Jul 24, 2015 at 5:32 AM, Dean Peterson <peterson dean gmail com> wrote:

Here is the build log:

Using bundler (1.3.5) 
I0722 20:35:37.777526 1 sti.go:388] Your bundle is complete!
I0722 20:35:37.777579 1 sti.go:388] It was installed into ./bundle
I0722 20:35:37.811400 1 sti.go:388] ---> Cleaning up unused ruby gems
I0722 20:35:42.736725 1 sti.go:131] Using provided push secret for pushing 172.30.13.89:5000/test/origin-ruby-sample image
I0722 20:35:42.736761 1 sti.go:134] Pushing 172.30.13.89:5000/test/origin-ruby-sample image ...
I0722 20:36:47.613637 1 sti.go:138] Successfully pushed 172.30.13.89:5000/test/origin-ruby-sample

And this is the deployment event error:

Failed to pull image "172.30.13.89:5000/test/origin-ruby-sample sha256:d7e1ed4818f45fc14a6ea98c622fddd81e2ab36caad8c94850952d8d150a2952": API error (500): v1 ping attempt failed with error: Get http://172.30.13.89:5000/v1/_ping: read tcp 172.30.13.89:5000: connection reset by peer


And this is my current running registry in the default namespace:

openshift]# ./oc get -n default se/docker-registry
NAME LABELS SELECTOR IP(S) PORT(S)
docker-registry docker-registry=default docker-registry=default 172.30.13.89 5000/TCP
[root localhost openshift]#



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

I now have a successful build that was pushed to the private registry. However, when deploying the frontend portion of the sample-app, I get the following error in the event logs:

Failed to pull image "172.30.13.89:5000/test/origin-ruby-sample sha256:d7e1ed4818f45fc14a6ea98c622fddd81e2ab36caad8c94850952d8d150a2952": API error (500): v1 ping attempt failed with error: Get http://172.30.13.89:5000/v1/_ping: read tcp 172.30.13.89:5000: connection reset by peer

How is it, the build portion of the process can see the registry and push to it, but the front end deployment piece is unable to pull the image that was just pushed?



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




--
Kenjiro NAKAYAMA <nakayamakenjiro gmail com>
GPG Key fingerprint = ED8F 049D E67A 727D 9A44  8E25 F44B E208 C946 5EB9


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