# Kibana instances increasing on Docker

**URL:** <https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830>\
**Category:** Kibana\
**Created:** [January 7, 2017, 12:06am UTC](https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830 "2017-01-07T00:06:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinoj\_Mathew](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@Vinoj\_Mathew](https://discuss.elastic.co/u/Vinoj_Mathew)\
**Post date:** [January 7, 2017, 12:06am UTC](https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830/1 "2017-01-07T00:06:01Z")

</div>

I am trying to run kibana5.1 and elasticsearch5.1 on docker using docker-compose.

1. Using volumes for elastic search data
2. Using volume for kibana config file

The challenge I am facing is when I use monitoring on kibana dashboard the no.of instances is increasing each time when I bounce docker-compose

• When I clear the elastic volumes for data indices first time the no.of instances show up 1  
• Second time its increases to 2 …. So on  
• If we clear the elastic volume data and bounce again the instance will be 1 and again each time we bounce the no.of instances increase for kibana

Any help is really appreciated.

Thanks

 ![](https://us1.discourse-cdn.com/elastic/original/2X/f/f8277c768cd3cd8c651dce68293e8354c81830aa.png)

---

<div class="post-metadata">

**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\
**Post date:** [January 7, 2017, 1:27am UTC](https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830/2 "2017-01-07T01:27:33Z")

</div>

Hi Vinoj,

Like Elasticsearch, [Kibana writes a Persistent UUID](https://github.com/elastic/kibana/issues/6378) when it first launches to disk. If you keep destroying the Kibana directory, then it will represent a unique instance when it restarts, even with the same configuration.

It sounds like you should probably be setting `path.data` in the `kibana.yml` to something that will survive the destruction of the Kibana folders. It's also important that multiple Kibana instances should _not_ share a data path.

For what it's worth, the instance count is relative to the timer in the top right. It _sees_ 2 instances in that timeframe (I'm guessing 1 hour or 15 minutes). Once the instance no longer exists in the given timeframe, it will disappear from the overview.

Hope that helps,  
Chris

---

<div class="post-metadata">

**Author:** ![Vinoj\_Mathew](https://avatars.discourse-cdn.com/v4/letter/v/d2c977/32.png) [@Vinoj\_Mathew](https://discuss.elastic.co/u/Vinoj_Mathew)\
**Post date:** [January 13, 2017, 4:51am UTC](https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830/3 "2017-01-13T04:51:53Z")

</div>

Thanks [chriS.it](http://chriS.it) works fine when i map the /usr/share/kibana/data as Volume

---

<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:** [February 10, 2017, 4:52am UTC](https://discuss.elastic.co/t/kibana-instances-increasing-on-docker/70830/4 "2017-02-10T04:52:13Z")

</div>

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