I am trying to do a setup like this: machine1 - 192.168.0.10
9300 => 9300 Docker container elasticsearch1 internal vlan 172.17.0.68 Elasticsearch transport running on port 9300 network.publish_host 192.168.10:9300 9301 => 9300 Docker container elasticsearch2 internal vlan 172.17.0.69 Elasticsearch transport running on port 9300 network.publish_host 192.168.10:9301 machine2 - 192.168.0.20 9300 => 9300 Docker container elasticsearch1 internal vlan 172.17.0.68 Elasticsearch transport running on port 9300 network.publish_host 192.168.20:9300 9301 => 9300 Docker container elasticsearch2 internal vlan 172.17.0.69 Elasticsearch transport running on port 9300 network.publish_host 192.168.20:9301 So if I define machine1 / elasticsearch1 as my master, I should be able to set unicast on the three other nodes as 192.168.0.10:9300, and as listed above, the network.publish_host on each node, BUT Each node in its docker container does not see the address it should be publishing, and it seems that this setting not only says "publish this address" but also "bind to this address". *Is there any way to publish an address which the node cannot actually bind to to allow machines in this type of a constellation to connect to each other?* Thank you! -Robin- -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ababbf50-ecae-4988-a4a0-af4ea2fb7412%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
