I tried to create Kibana and Elasticsearch and it seems that Kibana is having trouble identifying Elasticsearch.
Here are my steps:
1) Create network
docker network create mynetwork --driver=bridge
2) Run Elasticsearch Container
docker run -d -p 9200:9200 -p 9300:9300 --name elasticsearch_2_4 --network mynetwork elasticsearch:2.4
3) Run Kibana Container
docker run -i --network mynetwork -p 5601:5601 kibana:4.6
I get a JSON output when I connect to Elasticsearch via http://localhost:9200/ through my browser.
But when I open http://localhost:5601/ I get
Unable to connect to Elasticsearch at http://elasticsearch:9200.
Alternate Approach,
I still get a similar error when I try
docker run -d -e ELASTICSEARCH_URL=http://127.0.0.1:9200 -p 5601:5601 kibana:4.6
where I get the error
Unable to connect to Elasticsearch at http://127.0.0.1:9200.
My blog post based on the accepted answer: https://gunith.github.io/docker-kibana-elasticsearch/
Test:
You can test with your host ip or the ip identified by docker0 in ifconfig
Regards
There is some misunderstanding about what
localhost
or127.0.0.1
means when running a command inside a container. Because every container has its own networking,localhost
is not your real host system but either the container itself. So when you are running kibana and pointing theELASTICSEARCH_URL
variable tolocalhost:9200
the kibana process will look for elasticsearch inside the kibana container which of course isn't running there.You already introduced some custom network that you referenced when starting the containers. All containers running in the same network can reference each other via name on their
expose
d ports (see Dockerfiles). As you named your elasticsearch containerelasticsearch_2_4
, you can reference the http endpoint of elasticsearch ashttp://elasticsearch_2_4:9200
.As long as you don't need to access the elasticsearch instance directly, you can even omit mapping the ports 9200 and 9300 to your host.
Instead of starting all containers on their own, I would also suggest to use
docker-compose
to manage all services and parameters. You should also consider mounting a local folder as volume to have the data persisted. This could be your compose file. Add thenetworks
, if you need to have the external network, otherwise this setup just creates a network for you.I changed network configuration for Kibana container and after this it works fine: