# Install Elasticsearch with Docker **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [September 4, 2023, 2:31pm UTC](https://discuss.elastic.co/t/install-elasticsearch-with-docker/342271 "2023-09-04T14:31:15Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [September 4, 2023, 5:25pm UTC](https://discuss.elastic.co/t/install-elasticsearch-with-docker/342271/11 "2023-09-04T17:25:50Z")
Hi @alexus Assuming you followed the exact directions in the documents... Sometimes the cluster may not come up just for whatever reason. And that really is just a sample. And the problem is if it does not come up the first time you can try running it over and over and over again and it will not come up. What I have found you need to do is completely clean up, shut down and prune all the mounts and everything and then try again. We've had several users have the same experience and this is how they got it to work. Take a look at this > [@The stack cannot be started according to the instructions](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/11): > > So I reran from scratch and when I say scratch I mean reallly scratch I ran a docker system prune -a It ran fine Here is my output. $ docker-compose up -d ..... Lots of images being pulled ⠿ b2180a238095 Pull complete 98.0s [+] Running 6/6 ⠿ Network test\_default Created 0.1s ⠿ Container test-setup-1 Healthy … --- _[View the full topic](https://discuss.elastic.co/t/install-elasticsearch-with-docker/342271)._