Skip to content
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

ElasticSearch 8.x ver can't start because of xpack.security enabled #3290

Closed
makowskid opened this issue Oct 21, 2022 · 2 comments · Fixed by #3332
Closed

ElasticSearch 8.x ver can't start because of xpack.security enabled #3290

makowskid opened this issue Oct 21, 2022 · 2 comments · Fixed by #3332

Comments

@makowskid
Copy link
Contributor

Description:

ElasticSearch 8.x ver can't start because of xpack.security enabled. Need to disable it to start.

Expected Behavior:

ELK should start

Context information:

Output of git rev-parse HEAD

6dba2394628ee342b02e93003f3b931dd7c76857

Output of docker version

Docker version 20.10.17, build 100c701

Output of docker-compose version

docker-compose version 1.29.2, build 5becea4c

System info: Mac, Windows or Linux. Include which disto/version

[Ubuntu 20.04.5 LTS (Focal Fossa) on Windows 11 WSL 2

Linux 5.15.68.1-microsoft-standard-WSL2 #1 SMP Mon Sep 19 19:14:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the issue:

docker-compose up -d elasticsearch

Stacktrace & Additional info:

I was able to start it after changing docker-compose.yml

diff --git a/docker-compose.yml b/docker-compose.yml
index 74fb92c..7768af7 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -1033,6 +1033,8 @@ services:
         - cluster.name=laradock-cluster
         - node.name=laradock-node
         - bootstrap.memory_lock=true
+        - xpack.security.enabled=false
+        - xpack.security.transport.ssl.enabled=false
         - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
         - cluster.initial_master_nodes=laradock-node
@eriwin
Copy link

eriwin commented Dec 16, 2022

I can confirm this issue. I experienced it too. The change proposed by @makowskid solved the problem.

@makowskid
Copy link
Contributor Author

@bestlong thanks! merge appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants