-
Notifications
You must be signed in to change notification settings - Fork 134
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 file is not working #2
Comments
Hi @IamGroot19 ! Thank you so much for bringing this to my attention and for sharing a solution with our Beginner Community! I am sorry for the delay in response. I've been out of office from April 28th - May 14th and I am just seeing your message. I have reached out to the our wonderful community member who has contributed the Docker compose file to see what could have caused this issue. I will update this issue as soon as I hear back. Thank you again for your wonderful contribution. I appreciate you!! |
Hello @IamGroot19 hope you're doing great 😃 , After launching the Regards, |
Hi @IamGroot19 I double check the docker compose file and according to the definitions both container should be running in the same docker network with name
Have you check the output with |
Hi @LisaHJung @h3ct0rjs - apologies, i completely missed out on the notification. I cloned the repo and ran the docker-compose file . Here is the error log
|
Hi @IamGroot19 hope you're doing great. I check the log errors that you share with us but this seems like a local problem, I also found this : It seems like is a problem of permisssions, could you check this. Regards, |
I think the issue is something related to network configs, but I am not sure.
I eventually ended up using this: https://www.elastic.co/guide/en/elastic-stack-get-started/7.11/get-started-docker.html
Thought I'd file the issue to let others know.
The text was updated successfully, but these errors were encountered: