# ImagePullBackOff error while deploying Elastic via ECK

**URL:** <https://discuss.elastic.co/t/imagepullbackoff-error-while-deploying-elastic-via-eck/316739>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** docker\
**Created:** [October 17, 2022, 7:38am UTC](https://discuss.elastic.co/t/imagepullbackoff-error-while-deploying-elastic-via-eck/316739 "2022-10-17T07:38:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kylemclaren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kylemclaren/32/100720_2.png) [@kylemclaren](https://discuss.elastic.co/u/kylemclaren)\
**Post date:** [October 18, 2022, 7:59pm UTC](https://discuss.elastic.co/t/imagepullbackoff-error-while-deploying-elastic-via-eck/316739/2 "2022-10-18T19:59:52Z")

</div>

Hi @alytkowski,

**Edit** : `imagePullPolicy: IfNotPresent` will work too, but `Never` is the nuclear option!

Indeed, it looks like there is an [open issue](https://github.com/kubernetes/minikube/issues/14789) with minikube and one of the recommended workarounds is to manually pull the image, as you did.

First, I would recommend that you confirm the image is loaded into the minikube cluster: `minikube ssh docker images | grep elasticsearch`

Then, you can use a slightly altered version of the manifest that we have in the docs to force k8s to use the local image instead of trying to pull it, by setting `imagePullPolicy: Never`

```yaml
cat <<EOF | kubectl apply -f -
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: quickstart
spec:
  version: 8.4.3
  nodeSets:
  - name: default
    count: 1
    config:
      node.store.allow_mmap: false
    podTemplate:
      spec:
        containers:
        - name: elasticsearch
          imagePullPolicy: Never
EOF

```

Hope this works for you 🍻

---

_[View the full topic](https://discuss.elastic.co/t/imagepullbackoff-error-while-deploying-elastic-via-eck/316739)._