Are you starting it up in daemon mode? If not you will have logs on your screen, these should provide some kind of information about what the problem is. I have used this docker compose file and it works fine for me.
Thanks for the reply Tony. No I am not starting it in daemon mode, no errors are coming up. I’m running on a 2016 Macbook pro for work.
I decided to run the docker compose on my personal machine and it worked fine there, it was a Windows box with WSL 2 for the docker backend. So I’m guessing there’s a issue of not enough resources allocated to the Docker VM on my Mac perhaps. I am going to experiment with that and will post what I did just in case someone else has this issue.
Everything in brew is updated. Changing the resources available to the Docker Engine fixed my issue.
Before I had 2 CPU’s, 6144 MB of ram allocated.
Now I have 4 CPU’s, 8192 MB of ram allocated.
Whereas before it would just hang on the “Loading Elastic” splash screen, it booted basically instantly. I’m guessing it was the number of CPU’s? Seems a bit strange.
This is a known issue. Elasticsearch in general needs a lot of hardware resources to successfully run. You can read more about it here: Troubleshoot - Open Distro Documentation
@cassouza This will be different if you’re using the official Docker Desktop GUI, but I’m not, just the CLI. Here’s what I did to get the 4 CPU’s and 8192 MB of RAM above:
default was the name of the VM docker was using, so yours may be different. Also this is on a Mac, so Docker used VirtualBox, on other OS’s I believe that’s different.