# 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:** 9

<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 13, 2016, 6:30pm 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/9 "2016-04-13T18:30:26Z")

</div>

Whatever you use, you need to make sure that the IP address and ports for the VMs are properly set for `discovery.zen.ping.unicast.hosts` and that those are visible to other VMs and their corresponding containers.

---

_[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)._