Fix an issue with elasticsearch container #1166
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds functionality to disable ElasticSearch security if the service fails to start and stops after approximately 150 seconds with the
container for service "elasticsearch" is unhealthy
error to thecompose.yaml
file for theElasticSearch
service. The comment provides guidance on how to disable security features in ElasticSearch to resolve issues #1165 and #1159.Included the environment variable
xpack.security.enabled=false
within the comment, which can be uncommented by users if needed.For local development environments, configuring ElasticSearch with security disabled can simplify setup and avoid common issues related to security configuration.
@markshust if you have a better idea feel free to edit this PR.