# Elasticsearch version 2.x can not start in docker container but 1.7.3 starts with same config

**URL:** <https://discuss.elastic.co/t/elasticsearch-version-2-x-can-not-start-in-docker-container-but-1-7-3-starts-with-same-config/47141>\
**Category:** Elasticsearch\
**Created:** [April 12, 2016, 3:37pm UTC](https://discuss.elastic.co/t/elasticsearch-version-2-x-can-not-start-in-docker-container-but-1-7-3-starts-with-same-config/47141 "2016-04-12T15:37:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![abhijat](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@abhijat](https://discuss.elastic.co/u/abhijat)\
**Post date:** [April 12, 2016, 6:03pm UTC](https://discuss.elastic.co/t/elasticsearch-version-2-x-can-not-start-in-docker-container-but-1-7-3-starts-with-same-config/47141/2 "2016-04-12T18:03:35Z")

</div>

> [@ajay\_bh111](#):
>
> discovery.zen.ping.unicast.hosts: ["${ES\_ENV\_M1}:9300","${ES\_ENV\_M2}:9300","${ES\_ENV\_M3}:9300"]

Do you have three containers (one for each master) under the same VM? Or a single container running three ES nodes?

If three separate containers are involved then have you tried the setting

> network.publish\_host=$(docker-machine ip default)

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-version-2-x-can-not-start-in-docker-container-but-1-7-3-starts-with-same-config/47141)._