# ElasticSearch failed to apply default image tag in OpenShift deployment

**URL:** https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630
**Category:** Elasticsearch
**Tags:** docker
**Created:** [February 19, 2024, 7:11pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630 "2024-02-19T19:11:20Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Mike\_Kirby](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_kirby/32/125425_2.png) [@Mike\_Kirby](https://discuss.elastic.co/u/Mike_Kirby)
#### Post date: [February 19, 2024, 7:11pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630/1 "2024-02-19T19:11:20Z")

</div>

Good Afternoon my Elastic Guru's. I am in the process of using the Docker image of 8.11.4 to deploy Elasticsearch in an OpenShift envirorment. I am using the OpenShift User interface and it should be a simple enough task, however when I deploy Elasticsearch it creates the 3 pods, which is good. When I click inside one of the 3 pods that have been created it shows the following

```auto
elasticsearch-es-default-1 init:InvalidImageName

```

When I review the Events I am given the following message:

```auto
failed to apply default image tag "podman pull quay.our.internal.ca:8443/mkirby924/elasticsiem": couldn't parse image reference "podman pull quay.our.internal.ca:8443/mkirby924/elasticsiem":invalid reference format

```

The above error is shown on all three pods and it does not matter if I use the docker pull or the podman pull from our internal quay website.

I uploaded the image for Elasticsearch 8.11.4 from a linux machine connected to the quay using

```auto
podman tag <image_id> quay.our.internal.ca:8443/mkirby924/elastticsiem:elasticsearch

podman push --tls-verify=false quay.our.internal.ca:8443/mkirby924/elasticsiem:elasticsearch

```

I verified that the file made it up to our internal quay server.

 ![quay](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f2b3351d64b65b65aaf1f0ee649b352cb6b8ac5.png)

I am not sure what is wrong with my install, but it should be find from everything I have seen. I have even tried with 2 seperate quay repositories

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [February 20, 2024, 3:31am UTC](https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630/2 "2024-02-20T03:31:46Z")

</div>

Hello,

I'm not sure how this is an Elasticsearch issue, everything you shared is related to podman/openshift.

It is not clear what is your issue with any Elastic tool.

---

<div class="post-metadata">

### Author: ![Mike\_Kirby](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mike_kirby/32/125425_2.png) [@Mike\_Kirby](https://discuss.elastic.co/u/Mike_Kirby)
#### Post date: [February 20, 2024, 12:54pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630/3 "2024-02-20T12:54:20Z")

</div>

Thought I would post up here in case anyone else had come up against a similar issue when deploying Elasticsearch in an OpenShift environment. It is on a Linux Backbone with containers.

Thanks for the reply.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 19, 2024, 12:54pm UTC](https://discuss.elastic.co/t/elasticsearch-failed-to-apply-default-image-tag-in-openshift-deployment/353630/4 "2024-03-19T12:54:28Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.