# About an exception when running ES-2.4.6-alpine in a docker-compose file

**URL:** <https://discuss.elastic.co/t/about-an-exception-when-running-es-2-4-6-alpine-in-a-docker-compose-file/131923>\
**Category:** Elasticsearch\
**Created:** [May 15, 2018, 11:59am UTC](https://discuss.elastic.co/t/about-an-exception-when-running-es-2-4-6-alpine-in-a-docker-compose-file/131923 "2018-05-15T11:59:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alonsoir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alonsoir/32/31136_2.png) [@alonsoir](https://discuss.elastic.co/u/alonsoir)\
**Post date:** [May 15, 2018, 11:59am UTC](https://discuss.elastic.co/t/about-an-exception-when-running-es-2-4-6-alpine-in-a-docker-compose-file/131923/1 "2018-05-15T11:59:08Z")

</div>

Hi, i have a problem running ES-2.4.6-alpine within a docker container, i just had written the post in Stackoverflow, this is the [link](https://stackoverflow.com/questions/50335712/about-an-error-running-a-docker-compose-file-with-kafka-zookeeper-and-elastic-s).

I have read in this forum all the posts related with my issue, i think none of them are related with my issue, but i hope one of you could help me. I have to use this old version of ES because of spring-data framework. ES latest version is not ready to use with spring-data, last time i have seen.

Basically i am getting this exception:

```
demo-kafka-elastic_1 | Caused by: org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{elastic}{172.21.0.6:9300}]

```

[fullstacktrace link](https://pastebin.com/AtLGPkRk)

This is my docker-compose.yml, [pastebin link](https://pastebin.com/hH0a29m0)

Please help, if i run the same processes in local mode, it works fine, but when i run them with docker-compose, the exception happens. My apologies if this question is not for this forum, i have done the same question in docker forums and they are sending me to this forum.

Alonso

---

<div class="post-metadata">

**Author:** ![alonsoir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alonsoir/32/31136_2.png) [@alonsoir](https://discuss.elastic.co/u/alonsoir)\
**Post date:** [May 15, 2018, 5:25pm UTC](https://discuss.elastic.co/t/about-an-exception-when-running-es-2-4-6-alpine-in-a-docker-compose-file/131923/2 "2018-05-15T17:25:42Z")

</div>

I reply myself, the problem was in my application.properties file with a field named spring.data.elasticsearch.cluster-name=elasticsearch\_aironman  
that was interfering with

> cluster.name

environment variable docker-compose file.

Deleting the line from application.properties did the trick.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 12, 2018, 5:25pm UTC](https://discuss.elastic.co/t/about-an-exception-when-running-es-2-4-6-alpine-in-a-docker-compose-file/131923/3 "2018-06-12T17:25:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.