# Which network.host to use to connect nodes running inside docker-containers on separate machines?

**URL:** <https://discuss.elastic.co/t/which-network-host-to-use-to-connect-nodes-running-inside-docker-containers-on-separate-machines/153204>\
**Category:** Elasticsearch\
**Created:** [October 19, 2018, 5:02pm UTC](https://discuss.elastic.co/t/which-network-host-to-use-to-connect-nodes-running-inside-docker-containers-on-separate-machines/153204 "2018-10-19T17:02:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bluecoffee](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@bluecoffee](https://discuss.elastic.co/u/bluecoffee)\
**Post date:** [November 13, 2018, 1:12pm UTC](https://discuss.elastic.co/t/which-network-host-to-use-to-connect-nodes-running-inside-docker-containers-on-separate-machines/153204/3 "2018-11-13T13:12:56Z")

</div>

For the forum:

Hi,  
I found the solution. I need to separately set the network.bind\_host and the network.publish\_host:

```auto
      - network.bind_host=0.0.0.0
      - network.publish_host=136.xxx.xxx.xxx # or FQDM

```

PS: For those from the future who stumble over the same problem - I had also tried using some of the special values for network.host, e.g. `_global_`, which gives this exception:

```auto
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: No up-and-running global-scope (public) addresses found, got [name:lo (lo), name:eth0 (eth0)]

```

---

_[View the full topic](https://discuss.elastic.co/t/which-network-host-to-use-to-connect-nodes-running-inside-docker-containers-on-separate-machines/153204)._