# Kibana server is not ready yet (Docker) **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [July 27, 2024, 4:44pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-docker/363908 "2024-07-27T16:44:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![g0nz0](https://avatars.discourse-cdn.com/v4/letter/g/b5e925/32.png) [@g0nz0](https://discuss.elastic.co/u/g0nz0)\ **Post date:** [July 27, 2024, 4:44pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-docker/363908/1 "2024-07-27T16:44:27Z")
Hello, I've been following this guide below and got it working at work yesterday with little problems. > **[ElastiFlow-Tools/docker\_install at main · elastiflow/ElastiFlow-Tools](https://github.com/elastiflow/ElastiFlow-Tools/tree/main/docker_install)** > > Script to easily install ElastiFlow for ElasticSearch with all dependencies - elastiflow/ElastiFlow-Tools Today I built a new Ubuntu VM in a lab to build another instance of it, but Kibana just shows as starting and I can't work out why. They only difference I can see is I'm running a later version of Ubuntu, Docker and Docker Compose. ```auto sudo docker-compose -f elasticsearch_kibana_compose.yml -f elastiflow_compose.yml up -d WARN[0000] /opt/mydocker/elasticsearch_kibana_compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion [+] Running 32/32 ✔ setup Pulled 37.5s ✔ daff15ec8f7a Pull complete 5.7s ✔ 5e974df39f56 Pull complete 5.8s ✔ ca0a6c84a400 Pull complete 31.9s ✔ 053ff83dfd55 Pull complete 33.7s ✔ 5099f31692ae Pull complete 33.9s ✔ 7872d57a55e2 Pull complete 34.1s ✔ c4494268c1b9 Pull complete 34.3s ✔ 3dc715decf81 Pull complete 34.4s ✔ flow-collector Pulled 9.4s ✔ 3713021b0277 Pull complete 2.9s ✔ 51cc3e481c0f Pull complete 5.4s ✔ 7effbd6401e2 Pull complete 5.4s ✔ 4f4fb700ef54 Pull complete 5.7s ✔ 3fa53c56ee85 Pull complete 6.7s ✔ 5e5e0eaab342 Pull complete 6.9s ✔ es01 Pulled 37.5s ✔ kibana Pulled 50.2s ✔ c77c43ced6a3 Pull complete 2.9s ✔ dd5710f340d1 Pull complete 4.0s ✔ 3ba3c7a47ac3 Pull complete 4.1s ✔ ce8674f48262 Pull complete 4.2s ✔ 6513c8265527 Pull complete 4.7s ✔ 4ca545ee6d5d Pull complete 6.1s ✔ 7ca42f5e1f9f Pull complete 5.2s ✔ 15bc200ed7c0 Pull complete 46.3s ✔ bd6f992daf98 Pull complete 46.5s ✔ 8a343ae69360 Pull complete 46.6s ✔ 5dcd905a95b3 Pull complete 46.7s ✔ a1d670dcf42c Pull complete 46.8s ✔ 869527b2ac4c Pull complete 46.9s ✔ 6b1b1ca6cdf1 Pull complete 47.1s [+] Running 5/5 ✔ Network mydocker_default Created 0.1s ✔ Container mydocker-setup-1 Healthy 6.0s ✔ Container flow-collector Started 4.4s ✔ Container mydocker-es01-1 Healthy 33.6s ✔ Container mydocker-kibana-1 Started ``` Docker ```auto CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 11fbfca91bf9 docker.elastic.co/kibana/kibana:8.14.0 "/bin/tini -- /usr/l…" About a minute ago Up About a minute (health: starting) 0.0.0.0:5601->5601/tcp, :::5601->5601/tcp mydocker-kibana-1 553d48850928 docker.elastic.co/elasticsearch/elasticsearch:8.14.0 "/bin/tini -- /usr/l…" About a minute ago Up About a minute (healthy) 9200/tcp, 9300/tcp mydocker-setup-1 030b6f841fff elastiflow/flow-collector:7.1.1 "/bin/sh -c $BINARY_…" About a minute ago Up About a minute flow-collector ``` The only error I see in the Kibana container logs are: ```auto [2024-07-27T16:27:36.800+00:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. getaddrinfo EAI_AGAIN es01 ``` Versions I'm on: ```auto Docker version 27.1.1, build 6312585 Docker Compose version v2.29.1 ``` My .env file: ```auto # Password for the 'elastic' user (at least 6 characters) ELASTIC_PASSWORD=Spurs123! # Password for the 'kibana_system' user (at least 6 characters) KIBANA_PASSWORD=Spurs321! # Version of Elastic products STACK_VERSION=8.14.0 # Set the cluster name CLUSTER_NAME=docker-cluster # Set to 'basic' or 'trial' to automatically start the 30-day trial LICENSE=basic #LICENSE=trial # Port to expose Elasticsearch HTTP API to the host ES_PORT=9200 #ES_PORT=127.0.0.1:9200 # Port to expose Kibana to the host KIBANA_PORT=5601 #KIBANA_PORT=80 # Increase or decrease based on the available host memory (in bytes) MEM_LIMIT=1073741824 # Project namespace (defaults to the current folder name if not set) #COMPOSE_PROJECT_NAME=myproject # ElastiFlow Version ELASTIFLOW_VERSION=7.1.1 ``` What is interesting if I try and logs at the logs in the container for elasticsearch: ```auto sudo docker logs 553d48850928 Setting file permissions Waiting for Elasticsearch availability Setting kibana_system password ``` Thanks for any advise/help. ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [July 29, 2024, 9:04pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-docker/363908/2 "2024-07-29T21:04:13Z")
Hello, We are not responsible for Elastiflow so, I am not sure whats happening there. If you want to get set up using official elastic stack then these are our docs - [Install Elasticsearch with Docker | Elasticsearch Guide [8.14] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html) [Install Kibana with Docker | Kibana Guide [8.14] | Elastic](https://www.elastic.co/guide/en/kibana/current/docker.html) Thanks, bhavya