Thanks for the fast reply and sry for not providing it. I thought its the default error when the discovery type is not single-node
elasticsearch-1 | {"@timestamp":"2025-11-20T16:21:00.046Z", "log.level":"ERROR", "message":"node validation exception\n[1] bootstrap checks failed. You must address the points described in the following [1] lines before starting Elasticsearch. For more information see [``https://www.elastic.co/docs/deploy-manage/deploy/self-managed/bootstrap-checks?version=9.2``]\nbootstrap check failure [1] of [1]: the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured; for more information see [``https://www.elastic.co/docs/deploy-manage/deploy/self-managed/bootstrap-checks?version=9.2#bootstrap-checks-discovery-configuration``]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.node.name":"909025164b3c","elasticsearch.cluster.name":"docker-cluster"}
I found this as related topic after I postet this: Es 7 and docker single node cluster
From the thread
Thanks, I'd still recommend making this more obvious in the docker documentation. There is an enormous amount of documentation and literally anyone trying out Elasticsearch via docker is going to run into this.
I think I am one of them.
I understand that using Elasticsearch as a single node is discouraged although I don't get if it would be bad even if the scale of the application is small (RAG App with not that many users as only company employes have access).
My goal for now is to get a proof of concept working locally. I just want to consume the API.
We currently plan to deploy it via Azure but maybe we might self host it. Because the node would not be accessable from the outside I might consider not setting up auth.