# How debug "ImagePullBackOff" when using local pipeline docker-registry

**URL:** <https://forums.suse.com/t/how-debug-imagepullbackoff-when-using-local-pipeline-docker-registry/14348>\
**Category:** SUSE Rancher Prime\
**Created:** [May 21, 2019, 4:21pm UTC](https://forums.suse.com/t/how-debug-imagepullbackoff-when-using-local-pipeline-docker-registry/14348 "2019-05-21T16:21:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rzuini](https://avatars.discourse-cdn.com/v4/letter/r/7ea924/32.png) [@rzuini](https://forums.suse.com/u/rzuini)\
**Post date:** [May 21, 2019, 4:21pm UTC](https://forums.suse.com/t/how-debug-imagepullbackoff-when-using-local-pipeline-docker-registry/14348/1 "2019-05-21T16:21:37Z")

</div>

Hi guys,

I’m configuring Rancher Pipeline to deploy a simple application in NodeJs. The pipeline execution ends with success but I am getting a error on Workload screen:

ImagePullBackOff: Back-off pulling image “127.0.0.1:34908/pipex:latest”

This is my deployment.yaml:

```
kind: Service
apiVersion: v1
metadata:
  name: pipex-service
spec:
  selector:
    app: pipex
  type: NodePort
  ports:
    - protocol: TCP
      port: 3000
      targetPort: 3000
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: pipex-deployment
  namespace: p-mhz4d-pipeline
  labels:
    app: pipex
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pipex
  template:
    metadata:
      labels:
        app: pipex
    spec:
      containers:
      - name: pipex
        image: 127.0.0.1:34908/pipex:latest
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 3000

```

I’m using docker-registry of pipeline context (ephemeral mode).

I read the official documentation and did not succeed. Can someone tell me the best way to configure a pipeline using the local docker-registry (created by default by Rancher Pipeline)?

Thanks

---

<div class="post-metadata">

**Author:** ![naisanza](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/naisanza/32/3120_2.png) [@naisanza](https://forums.suse.com/u/naisanza)\
**Post date:** [June 25, 2019, 3:12pm UTC](https://forums.suse.com/t/how-debug-imagepullbackoff-when-using-local-pipeline-docker-registry/14348/2 "2019-06-25T15:12:58Z")

</div>

You’ll want to add your private registry to Rancher

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/9/975cc60eb9ebb0e0508325be161028686834f301.png)

And then you can select it from your Pipeline configuration

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/f/f56820a2e36cc28160eaff463fa2bee36d0929bd.png)

And if you’re using an insecure private registry, you’ll need to add these lines to your Pipeline yaml (ONLY USE SPACES, NO TABS)

```auto
    env:
      PLUGIN_DEBUG: "true"
      PLUGIN_INSECURE: "true"

```

 ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/834f380bd327a4c42a4a07464a2a9074cebf690e.png)