appbaseio / reactivesearch-api-docker

9 stars 3 forks source link

docker-compose-with-elasticsearch throws the following error on appbase container startup #4

Open rajeshkp opened 3 years ago

rajeshkp commented 3 years ago

time="2021/04/10 13:50:31" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359" time="2021/04/10 13:50:31" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go :192" => port used 8000 time="2021/04/10 13:51:39" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359" time="2021/04/10 13:51:39" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go :192" => port used 8000 time="2021/04/10 13:52:46" level=error msg="[ElasticSearch: Error] => elastic: http://172.30.0.2:9200 is dead" file=" entry.go:359" time="2021/04/10 13:52:46" level=fatal msg="Error encountered: error while initializing elastic v7 client: no active connection found: no Elasticsearch node available" file=" logger.go :192"

rajeshkp commented 3 years ago

Appreciate any inputs on this

rajeshkp commented 3 years ago

Appreciate any inputs on this

Better-Boy commented 3 years ago

@siddharthlatest Can you please help here as I'm facing the same problem too?

Better-Boy commented 3 years ago

@lakhansamani Facing the following problem

appbase_configure    | starter.sh: applet not found
appbase_configure    | starter.sh: applet not found
appbase_configure    | starter.sh: applet not found
appbase              | => port used 8000
appbase              | time="2021/05/06 08:30:15" level=fatal msg="ES_CLUSTER_URL env required but not present" file=" entry.go:359"
appbase              | => port used 8000
rajeshkp commented 3 years ago

@lakhansamani @siddharthlatest appreciate your inputs on this issue

lakhansamani commented 3 years ago

@rajeshkp @Better-Boy thanks for reporting looking into it

lakhansamani commented 3 years ago

@rajeshkp @Better-Boy we have seen the applet issue with non intel machines. This happens because we trying to listen to file change in one of the containers. We trying to come up with a generic solution here, but till that this is an alternative that you can follow by using

docker-compose -f docker-compose-with-elasticsearch-without-nginx.yml up

Here is a quick demo of it https://www.loom.com/share/9f8d81c6ba5849dd9b373cec030d337d

Better-Boy commented 3 years ago

Thanks @lakhansamani It's working now