-
Notifications
You must be signed in to change notification settings - Fork 187
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
Docker-Compose issue "Kibana server is not ready yet" #663
Comments
I fixed this by setting the image for elastic-search to be
I'm happy to close this issue. Do you want me to update any documentation and create a PR to give back to the community? |
Happy to have a PR that fixes this issue! |
I'm working on getting it working on my other laptop which is an M2 (vs my M1) and running into some more issues that I will work out before submitting a PR. |
If you are able to run it in a M2 that will be so helpful because we don't have that processor on our computers, so we don't have a way to try everything there. |
I'm running into the same issues, but on M3. If you find a general fix, I'll happy to test it on M3. |
On my M2 based MacBook I got the example (default) docker compose setup working by changing the
The complete elasticsearch sections looks now like this: elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.17.21-arm64
command: elasticsearch -Enetwork.bind_host=0.0.0.0 -Ehttp.max_content_length=2000mb
ports:
- 9200:9200
environment:
- discovery.type=single-node
- ES_JAVA_OPTS=-Xms2g -Xmx2g
- ANONYMOUS_USER=true Further testing would be needed to check if "everything" is really working is expected 🤞🏻 |
When I try the
docker-compose up -d
setup, I run into an issue where localhost says "Kibana server is not ready yet"Machine is an
Apple M1
If I run the command
docker logs docker-compose-elasticsearch-1
I see an error like this:Is there a suggestion on what the best course of action is here?
Thank you so much for your help and for creating this software. I am looking forward to using it!
The text was updated successfully, but these errors were encountered: