# On Docker containers. Kibana connect to cloud instead the Elasticsearch container

**URL:** <https://discuss.elastic.co/t/on-docker-containers-kibana-connect-to-cloud-instead-the-elasticsearch-container/348336>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [November 30, 2023, 1:33pm UTC](https://discuss.elastic.co/t/on-docker-containers-kibana-connect-to-cloud-instead-the-elasticsearch-container/348336 "2023-11-30T13:33:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [December 1, 2023, 10:19pm UTC](https://discuss.elastic.co/t/on-docker-containers-kibana-connect-to-cloud-instead-the-elasticsearch-container/348336/2 "2023-12-01T22:19:14Z")

</div>

I think you didn't explain how you set up your kibana.yml, but since it doesn't connect to the cluster you want, it must have some invalid information.

The instructions I recommend are to use docker-compose for Elasticsearch nodes and Kibana.

Read the docs on running Elasticsearch in Docker-Compose: [Change Index Ingestion method](https://discuss.elastic.co/t/change-index-ingestion-method/348242)  
And the docs on running Kibana in Docker-compose: [Change Index Ingestion method](https://discuss.elastic.co/t/change-index-ingestion-method/348242)

Having all the services declared in a `docker-compose.yml` file will simplify the network configuration.

---

_[View the full topic](https://discuss.elastic.co/t/on-docker-containers-kibana-connect-to-cloud-instead-the-elasticsearch-container/348336)._