Closed s0p4L1n3 closed 4 months ago
With security disabled before the first initialization, it is likely that built-in users never get created, therefore this check will always fail.
Could you try again after adding exit 0
below this line?
https://github.com/deviantony/docker-elk/blob/120d860cce697e1cfbf772bf5654775201aa6bea/setup/entrypoint.sh#L70
sublog 'Elasticsearch is running'
+exit 0
Oh just like that, I understand now, I just tried with xpack.security.enabled: true
and the setup success BUT that was not my original goal in the begining.
My goal was to comment discovery.type: single-node
in the compose to enable "production" mode.
But then, bootstrap failed, because I need to set:
discovery.seed_hosts: elasticsearch
xpack.security.transport.ssl.enabled = true
But then xpack.security.transport.ssl.enable requires to put certificates for ELK and the CA to signed the certificates. After writing all this, I understand that production mode requires security with certs. So I can't have production mode and no certificates.
At this step, should I clone your tls branch ? Is it ok that the branch is 5 commit away from the main one? Last but no least, I have an enterprise Windows PKI with two tier model. Do you recommend to keep the self signed cert generated during the setup or its best to have my own certs signed by the PKI ?
Thank you !
That's correct, as pointed out in the README the production mode requires a few extra configurations. Enabling TLS is one prerequisite, but not the only one; one kernel parameter needs to be tweaked on the host as well, among other things.
Switching to the tls
branch sounds like the right thing to do if you want to have TLS enabled with a minimal effort.
The branch seems to be ahead of main
because it builds on top of main
(we rebase it regularly on top of it). So despite the appearances, it is in fact in-sync with main
, with TLS-specific additions on top.
Alright, thank you ! I will then try the tls branch.
Problem description
Hello, I'm trying to run your project, I've just edited to settings to elasticsearch.yml. And changed the passwords in .env. When I'm running
docker compose up setup
, it exit with code 1 Timed out waiting for condition, but I don't know what condition it is waiting ?Extra information
elasticsearch.yml changed
xpack.license.self_generated.type: trial --> to basic xpack.security.enabled: true --> to false
Stack configuration
Docker setup
Container logs