Hello everyone, I have an issue with the environment variable discovery.type=single-node when spinning up an Elasticsearch container via docker-compose: Sample docker-compose file as follows: elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch:7.10.1 restart: alway…

Problem solved. It was a side-effect of too many docker container with too little available memory. This was not an issue when running the isolated Elasticsearch container. The other error message came when running the isolated Elasticsearch docker container manually, without the discovery.type par…

Issue with too little memory, running several docker container (including Elasticsearch)

Elastic Stack Elasticsearch

system (system) Closed January 27, 2021, 8:37pm 6

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

Topic		Replies	Views
Elasticstash single node via docker-compose Elasticsearch	4	13908	June 18, 2019
Guide to Start a single-node cluster in Docker Elasticsearch docker	7	128	November 26, 2025
Es 7 and docker single node cluster Elasticsearch	4	3355	May 14, 2019
Setting up Elasticsearch with Docker on local machine - Container stops and throws error Elasticsearch docker	7	1689	March 18, 2020
The default discovery settings are unsuitable for production use; Elasticsearch	3	7718	June 11, 2019

Issue with too little memory, running several docker container (including Elasticsearch)

Related topics