# The stack cannot be started according to the instructions

**URL:** <https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [March 10, 2023, 9:26am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431 "2023-03-10T09:26:56Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**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:** [March 10, 2023, 3:39pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/11 "2023-03-10T15:39:33Z")

</div>

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.

```auto
$ 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 2.4s
 ⠿ Container test-es01-1 Healthy 74.1s
 ⠿ Container test-es02-1 Healthy 65.1s
 ⠿ Container test-es03-1 Healthy 66.1s
 ⠿ Container test-kibana-1 Started 74.3s

```

Everything came up and work, I even logged

I watched the video.

**I did notice that you did not clean up the volumes before trying the second time.**

**Also you should try to clean the container images... I did not see them get pulled, perhaps you have some leftover containers...**

Also noticed thatnetwork and volume drivers look different, the output looks different etc .... I am not sure if [portainer.io](http://portainer.io) is something different

Also after you clean all up and try again ... making sure the volumes on both the docker and host side are cleaned up try this

```auto
$ curl -k -u elastic:elastic https://localhost:9200
{
  "name" : "es01",
  "cluster_name" : "docker-cluster",
  "cluster_uuid" : "A9Uu3dPjTJWiJZ8hRkL1gA",
  "version" : {
    "number" : "8.6.2",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "2d58d0f136141f03239816a4e360a8d17b6d8f29",
    "build_date" : "2023-02-13T09:35:20.314882762Z",
    "build_snapshot" : false,
    "lucene_version" : "9.4.2",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "You Know, for Search"
}

```

---

_[View the full topic](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431)._