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

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"

Inizia riproducendo l’avvio del container appbase con la configurazione docker-compose ed Elasticsearch, quindi esamina l’errore di connessione segnalato in entry.go:359 e logger.go:192. Verifica perché Elasticsearch all’indirizzo 172.30.0.2:9200 non sia disponibile; il lavoro è completato quando il container si avvia senza l’errore “no active connection found”.

Scritto dal modello di indicizzazione a partire dal testo della issue.