# No node available : Elasticsearch Transport Client can't connect to Docker container

**URL:** <https://discuss.elastic.co/t/no-node-available-elasticsearch-transport-client-cant-connect-to-docker-container/94883>\
**Category:** Elasticsearch\
**Created:** [July 28, 2017, 12:46am UTC](https://discuss.elastic.co/t/no-node-available-elasticsearch-transport-client-cant-connect-to-docker-container/94883 "2017-07-28T00:46:00Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Jessec](https://avatars.discourse-cdn.com/v4/letter/j/9d8465/32.png) [@Jessec](https://discuss.elastic.co/u/Jessec)\
**Post date:** [July 28, 2017, 7:40pm UTC](https://discuss.elastic.co/t/no-node-available-elasticsearch-transport-client-cant-connect-to-docker-container/94883/8 "2017-07-28T19:40:30Z")

</div>

I solved the problem eventually.

By default the network ip for transport is 127.0.0.1 rather than 0.0.0.0. Because it's only listening to 127.0.0.1 rahter than all interfaces, when accessing from outside the container, the transport is not accessible. So I set it to 0.0.0.0.

The problem following this is reseting the ip address triggers the bootstrap checks, which fail due to map counts check. Running "sysctl -w vm.max\_map\_count=262144" solves the problem.

---

_[View the full topic](https://discuss.elastic.co/t/no-node-available-elasticsearch-transport-client-cant-connect-to-docker-container/94883)._