# Vagrant+docker+kibana

**URL:** <https://discuss.elastic.co/t/vagrant-docker-kibana/134074>\
**Category:** Elasticsearch\
**Created:** [May 31, 2018, 2:45pm UTC](https://discuss.elastic.co/t/vagrant-docker-kibana/134074 "2018-05-31T14:45:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alejandro\_Leon\_Mora](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alejandro_leon_mora/32/31791_2.png) [@Alejandro\_Leon\_Mora](https://discuss.elastic.co/u/Alejandro_Leon_Mora)\
**Post date:** [May 31, 2018, 2:45pm UTC](https://discuss.elastic.co/t/vagrant-docker-kibana/134074/1 "2018-05-31T14:45:35Z")

</div>

May 31, 2018 4:23 PM (Europe: Paris), May 31, 2018 7:23 AM (America: Los Angeles)

Hello!

I've created a [Vagrant multimachine script](https://gist.github.com/tutmosisII/e994b7458951bbd1cf078db67a354a54) to run an elasticsearch cluster and kibana. I'm using docker provisioning to create the cluster.

The first node (appes1) and Kibana start well and communicate each other. But the second node (appes2) does not communicate with the first one.

I think that the problem is that both nodes are listening in the internal ip that docker provides. I appreciate you help to finish this example.

The following error is produced in the second node:

[2018-05-31T14:41:43,918][WARN][o.e.d.z.ZenDiscovery] [appes2] failed to connect to master [{appes1}{Ji5cbCwAQbS57134Add7ww}{jEJlXkxsSLiq869zPCv53A}{172.17.0.2}{172.17.0.2:9300}{ml.machine\_memory=2097197056, ml.max\_open\_jobs=20, ml.enabled=true}], retrying...  
org.elasticsearch.transport.ConnectTransportException: [appes1][172.17.0.2:9300] handshake failed. unexpected remote node {appes2}{FyQBnGKeQlmr\_\_NVvJ2OLA}{J\_\_G7vKXT2W-nicsYOuCPg}{172.17.0.2}{172.17.0.2:9300}{ml.machine\_memory=2097197056, ml.max\_open\_jobs=20, ml.enabled=true}  
at org.elasticsearch.transport.TransportService.lambda$connectToNode$3(TransportService.java:335) ~[elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.transport.TcpTransport.connectToNode(TcpTransport.java:514) ~[elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:331) ~[elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.transport.TransportService.connectToNode(TransportService.java:318) ~[elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.discovery.zen.ZenDiscovery.joinElectedMaster(ZenDiscovery.java:515) [elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.discovery.zen.ZenDiscovery.innerJoinCluster(ZenDiscovery.java:483) [elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.discovery.zen.ZenDiscovery.access$2500(ZenDiscovery.java:90) [elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.discovery.zen.ZenDiscovery$JoinThreadControl$1.run(ZenDiscovery.java:1253) [elasticsearch-6.2.4.jar:6.2.4]  
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:573) [elasticsearch-6.2.4.jar:6.2.4]  
at java.util.concurrent.ThreadPoolExecuto

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [June 2, 2018, 1:56am UTC](https://discuss.elastic.co/t/vagrant-docker-kibana/134074/2 "2018-06-02T01:56:00Z")

</div>

I think you have an IP collision there. For the `network.host`, instead of `0.0.0.0`, try setting their respective `192.168.1.*` addresses.

---

<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:** [June 30, 2018, 1:56am UTC](https://discuss.elastic.co/t/vagrant-docker-kibana/134074/3 "2018-06-30T01:56:06Z")

</div>

Closed on June 30, 2018, 1:56am UTC

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