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

Pushing docker images to integrated registry



Hi there. 
I have a relatively new installation of Openshift v1.1.4.  

Im receiving a 500 Internal Server Error when attempting to push an image to the integrated registry.


[root agltstosm01 ~]# docker push ${REGISTRY}/openshift/availity-${IMAGENAME}

The push refers to a repository [172.30.142.84:5000/openshift/availity-node4] (len: 1)

99ac6fa1ed8b: Image already exists 

048f2c327eb2: Image already exists 

3d1e7129c127: Image already exists 

0272f950113d: Image already exists 

7e7a29d9e7c8: Image already exists 

6e1f6d2c8006: Image already exists 

c103704c1791: Image already exists 

ed2d5f83035e: Image already exists 

abf626c20041: Image already exists 

a00c22cda9db: Image already exists 

53b9121cb98c: Image already exists 

29539139bf9d: Image already exists 

a06b823c6a02: Image already exists 

df82ac64861d: Image already exists 

5e5f21412e19: Image already exists 

9ee13ca3b908: Image already exists 

latest: digest: sha256:ea11be0128fbf2275fe21cce3e407b7874d274a2f9d0fce2ee8cb426a393572b size: 56842

Received unexpected HTTP status: 500 Internal Server Error


It does not appear to create the image stream when I attempt the push.


Im using this script when attempting to push:

PATHTODOCKER=/root/node-4.2.3-docker
IMAGENAME="node4"
LOCALTAG="availity/${IMAGENAME}"
USERNAME="gfranczyk"
EMAIL="gfranczyk availity com"
REGISTRY=" 172.30.142.84:5000"
docker build -t ${LOCALTAG} ${PATHTODOCKER}
docker tag ${LOCALTAG} ${REGISTRY}/openshift/availity-${IMAGENAME}
oc login --certificate-authority /etc/origin/node/ca.crt  -u ${USERNAME}
oc project openshift
docker login -u ${USERNAME} -e ${EMAIL} -p "`oc whoami -t`"  ${REGISTRY}
docker push ${REGISTRY}/openshift/availity-${IMAGENAME}


The last few log entries in the docker registry are:

10.1.1.1 - - [18/Apr/2016:14:24:20 -0400] "PUT /v2/openshift/availity-node4/manifests/latest HTTP/1.1" 500 259 "" "docker/1.9.1 go/go1.4.2 kernel/3.10.0-327.10.1.el7.x86_64 os/linux arch/amd64"

time="2016-04-18T14:24:20.915753333-04:00" level=error msg="Error creating ImageStreamMapping: imagestreams \"availity-node4\" not found" go.version=go1.4.2 http.request.host="172.30.142.84:5000" http.request.id=fafd9ef6-3661-46ee-b723-d143691339a7 http.request.method=PUT http.request.remoteaddr="10.1.1.1:35194" http.request.uri="/v2/openshift/availity-node4/manifests/latest" http.request.useragent="docker/1.9.1 go/go1.4.2 kernel/3.10.0-327.10.1.el7.x86_64 os/linux arch/amd64" instance.id=74de4ff9-2af6-496e-b033-52e9711a4bd6 vars.name="openshift/availity-node4" vars.reference=latest 

time="2016-04-18T14:24:20.915933043-04:00" level=error msg="response completed with error" err.code=UNKNOWN err.detail="imagestreams \"availity-node4\" not found" err.message="unknown error" go.version=go1.4.2 http.request.host="172.30.142.84:5000" http.request.id=fafd9ef6-3661-46ee-b723-d143691339a7 http.request.method=PUT http.request.remoteaddr="10.1.1.1:35194" http.request.uri="/v2/openshift/availity-node4/manifests/latest" http.request.useragent="docker/1.9.1 go/go1.4.2 kernel/3.10.0-327.10.1.el7.x86_64 os/linux arch/amd64" http.response.contenttype="application/json; charset=utf-8" http.response.duration=70.84445ms http.response.status=500 http.response.written=259 instance.id=74de4ff9-2af6-496e-b033-52e9711a4bd6 vars.name="openshift/availity-node4" vars.reference=latest 

10.1.0.1 - - [18/Apr/2016:14:24:25 -0400] "GET /healthz HTTP/1.1" 200 0 "" "Go 1.1 package http"

10.1.0.1 - - [18/Apr/2016:14:24:25 -0400] "GET /healthz HTTP/1.1" 200 0 "" "Go 1.1 package http"

10.1.0.1 - - [18/Apr/2016:14:24:35 -0400] "GET /healthz HTTP/1.1" 200 0 "" "Go 1.1 package http"


Can someone explain what I am doing wrong?

Thanks!

Gary Franczyk
Senior Unix Administrator, Infrastructure

Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256
W 904.470.4953 | M 561.313.2866

Gary Franczyk availity com


The information contained in this e-mail may be privileged and confidential under applicable law. It is intended solely for the use of the person or firm named above. If the reader of this e-mail is not the intended recipient, please notify us immediately by returning the e-mail to the originating e-mail address. Availity, LLC is not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Availity, LLC.

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