# Kibana docker setup

**URL:** <https://discuss.elastic.co/t/kibana-docker-setup/285612>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [September 30, 2021, 3:43pm UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612 "2021-09-30T15:43:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alpine\_f1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alpine_f1/32/95302_2.png) [@alpine\_f1](https://discuss.elastic.co/u/alpine_f1)\
**Post date:** [September 30, 2021, 3:43pm UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612/1 "2021-09-30T15:43:58Z")

</div>

I am running Elasticsearch cluster (2 master, 2 data and 1 voter) as docker containers behind a load balanced setup. F5 URL for that looks like [https://myelastic.mycompany.com](https://myelastic.mycompany.com). I am also running Kibana container that connects to the elastic cluster. Kibana's F5 URL looks like [https://mykibana.mycompany.com](https://mykibana.mycompany.com).

I have currently configured my "ELASTICSEARCH\_HOSTS" to be '["[http://esdata1.mycompany.com:9200](http://esdata1.mycompany.com:9200)","[http://esdata2.mycompany.com:9200](http://esdata2.mycompany.com:9200)"]' and this entire setup works perfectly without any issues.

However I would like to use F5 URL in the "ELASTICSEARCH\_HOSTS" instead of specific cluster instance url. The reason is I have 2 datacenters where the entire stack gets deployed. And for each datacenter, I had to manually update the above environment variable with the correct instance url and I am trying to find a solution to avoid it. Is this even possible?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 30, 2021, 10:45pm UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612/2 "2021-09-30T22:45:29Z")

</div>

Welcome to our community! 😃

You should be able to do that, yes.

---

<div class="post-metadata">

**Author:** ![alpine\_f1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alpine_f1/32/95302_2.png) [@alpine\_f1](https://discuss.elastic.co/u/alpine_f1)\
**Post date:** [October 7, 2021, 6:41am UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612/3 "2021-10-07T06:41:41Z")

</div>

It didn’t work with load balancer url. It worked with the hostname of the cluster instance. So I went ahead with that.

---

<div class="post-metadata">

**Author:** ![alpine\_f1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alpine_f1/32/95302_2.png) [@alpine\_f1](https://discuss.elastic.co/u/alpine_f1)\
**Post date:** [October 15, 2021, 3:56am UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612/4 "2021-10-15T03:56:34Z")

</div>

@warkolm Here is the latest update. It worked with the load balanced url.

---

<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:** [November 12, 2021, 3:57am UTC](https://discuss.elastic.co/t/kibana-docker-setup/285612/5 "2021-11-12T03:57:07Z")

</div>

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