-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose-with-elasticsearch throws the following error on appbase container startup #4
Comments
Appreciate any inputs on this |
1 similar comment
Appreciate any inputs on this |
@siddharthlatest Can you please help here as I'm facing the same problem too? |
@lakhansamani Facing the following problem
|
@lakhansamani @siddharthlatest appreciate your inputs on this issue |
@rajeshkp @Better-Boy thanks for reporting looking into it |
@rajeshkp @Better-Boy we have seen the applet issue with non intel machines.
Here is a quick demo of it |
Thanks @lakhansamani It's working now |
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"
The text was updated successfully, but these errors were encountered: