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

Re: Cannot find image



after the creation of a new registry a registry server is listed:
docker ps
CONTAINER ID        IMAGE                                    COMMAND                CREATED              STATUS              PORTS                                                              NAMES
a548bde96ae2        openshift/origin-deployer:v1.0.2         "/usr/bin/openshift-   About a minute ago   Up About a minute                                                                      k8s_deployment.9d58524_docker-registry-1-deploy_default_ae236617-3467-11e5-af4d-001a4acf9901_9e31f7b6   
8756a3862da2        openshift/origin-pod:v1.0.2              "/pod"                 About a minute ago   Up About a minute                                                                      k8s_POD.d14ec42d_docker-registry-1-deploy_default_ae236617-3467-11e5-af4d-001a4acf9901_86698fcc         
54a44cba73d5        openshift/origin-haproxy-router:v1.0.2   "/usr/bin/openshift-   2 days ago           Up 2 days                                                                              k8s_router.414c33af_router-1-xgb7x_default_0f0fbde6-314f-11e5-af4d-001a4acf9901_f62eb3fc                
9ca696aaae6b        openshift/origin-pod:v1.0.2              "/pod"                 2 days ago           Up 2 days           0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:1936->1936/tcp   k8s_POD.e8692ccd_router-1-xgb7x_default_0f0fbde6-314f-11e5-af4d-001a4acf9901_deb960b0    

But after a bit the deployer fails. Since I have run this through a few times I have a bunch of old registry deployments show up with a docker ps -a. When I run a docker logs on the deployer I get:

docker logs a548bde96ae2 
I0727 13:59:22.950260       1 deployer.go:194] Deploying default/docker-registry-1 for the first time (replicas: 1)
I0727 13:59:22.954807       1 recreate.go:112] Scaling default/docker-registry-1 to 1 before validating first replica
F0727 14:01:24.001591       1 deployer.go:63] couldn't scale default/docker-registry-1 to 1: timed out waiting for the condition


When I run a docker logs on the registry server container itself I get nothing. I did notice that the registry servers storage for a test instance with loopback mount is supposed to be located at /var/lib/openshift/docker-registry but the docker-registry directory did not exist. I created it but that did not fix things. If it is needed it seems that the creation should be documented or be done by ansible. 
Anything further I can do to investigate? Thanks so much for all the help. 

On Mon, Jul 27, 2015 at 9:59 AM, Dan Mace <dmace redhat com> wrote:
On Mon, Jul 27, 2015 at 9:31 AM, Ben Parees <bparees redhat com> wrote:


On Mon, Jul 27, 2015 at 8:13 AM, Sco <spamboxy1 gmail com> wrote:
Sorry I should have been more specific, my response from above is from the build-log. It states that the image builds successfully but the push of the image fails.

I have done some additional troubleshooting and have found that what is happening is that the docker registry exits with code 255 when a build try to push an image to it. When you look at the logs for the registry is says that it could not scale...
Steps to produce error:
delete old project(test) with oc delete project/test, 
delete old registry from default project (deleted pod, build, deployment config, replication controller, route, service)
create new registry with documented command, oadm registry --create=true --redentials=/etc/openshift/master/openshift-registry.kubeconfig --mount-host=/var/lib/openshift/docker-registry
check to see that it is ok, oc get all :
NAME      TYPE      SOURCE
NAME      TYPE      STATUS    POD
NAME      DOCKER REPO   TAGS      UPDATED
NAME              TRIGGERS       LATEST VERSION
docker-registry   ConfigChange   1
router            ConfigChange   1
CONTROLLER          CONTAINER(S)   IMAGE(S)                                  SELECTOR                                                                                REPLICAS
docker-registry-1   registry       openshift/origin-docker-registry:v1.0.2   deployment=docker-registry-1,deploymentconfig=docker-registry,docker-registry=default   1
router-1            router         openshift/origin-haproxy-router:v1.0.2    deployment=router-1,deploymentconfig=router,router=router                               1
NAME      HOST/PORT   PATH      SERVICE   LABELS
NAME              LABELS                                    SELECTOR                  IP(S)           PORT(S)
docker-registry   docker-registry=default                   docker-registry=default   172.30.187.19   5000/TCP
kubernetes        component=apiserver,provider=kubernetes   <none>                    172.30.0.1      443/TCP
router            router=router                             router=router             172.30.2.117    80/TCP
NAME                       READY     REASON    RESTARTS   AGE
docker-registry-1-deploy   1/1       Running   0          2m
​​
router-1-xgb7x             1/1       Running   2          1d

make new test project and attempt to create new cakephp-example, build runs, at end of build it fails
build-logs say that it was unable to push the image (per previous email)
switch to default project and do, oc get all
see that docker registry has exited code 255

run oc logs docker-registry-1-deploy, and get:
I0724 18:32:19.604716       1 deployer.go:194] Deploying default/docker-registry-1 for the first time (replicas: 1)
I0724 18:32:19.608136       1 recreate.go:112] Scaling default/docker-registry-1 to 1 before validating first replica
F0724 18:34:20.692927       1 deployer.go:63] couldn't scale default/docker-registry-1 to 1: timed out waiting for the condition


it sounds like the registry pod actually failed to start.  what you're showing there are the logs for the attempt to deploy the registry pod, not the registry pod itself.

if you run "docker ps -a" is there any evidence an openshift/origin-docker-registry image was run recently?  if so, can you run "docker logs <containerid>" on the container?  It seems like the container is failing to start for some reason, which would cause the deployment to fail.

Dan Mace, any other debugging suggestions for this deployment failure?

​The deplo​yment error for the registry indicates that the registry replication controller (RC) couldn't be scaled up. This usually means that a pod couldn't be scheduled for some reason (like unsatisfied resource requirements, a node selector on the RC which doesn't match any registered nodes, or sometimes even mismatched node IP/hostnames).

Is there any output in the openshift master log related to pod scheduling failure for a registry pod? Something like "failed to find fit for pod..." Are there any events which indicate a scheduling failure?
 
On Fri, Jul 24, 2015 at 12:52 PM, Ben Parees <bparees redhat com> wrote:
has a build run for cakephp?  did it complete successfully?  if not, what do the logs look like?


On Fri, Jul 24, 2015 at 9:29 AM, Sco <spamboxy1 gmail com> wrote:
The built in templates for origin are not working for me when following the install guide (https://github.com/openshift/openshift-ansible/blob/master/README_origin.md).
I am currently running a master and a single node, with the master in the node group. 
I change to the test project I created, oc project test, then issue the command to build a cake-php example, oc deploy cakephp-frontend --latest -n test, and get Starting build. when I then issue a oc get all, the output looks like this:

NAME               LABELS                     SELECTOR                IP(S)           PORT(S)
cakephp-frontend   template=cakephp-example   name=cakephp-frontend   172.30.37.77    8080/TCP
dancer-frontend    template=dancer-example    name=dancer-frontend    172.30.253.17   8080/TCP
NAME                        READY     REASON                                                  RESTARTS   AGE
cakephp-example-1-build     0/1       ExitCode:255                                            0          19h
cakephp-frontend-1-8ljmt    0/1       Error: image library/cakephp-example:latest not found   0          45s
cakephp-frontend-1-deploy   1/1       Running                                                 0          47s


When I check  /etc/sysconfig/docker, there is not image source specified. How and what should the image library be set to for OSO?


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




--
Ben Parees | OpenShift



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




--
Ben Parees | OpenShift




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