# 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:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 9:26am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/1 "2023-03-10T09:26:56Z")

</div>

I'm trying to run the stack in docker according to [this instruction](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-compose-file).

My `.env`:

```auto
# Password for the 'elastic' user (at least 6 characters)
ELASTIC_PASSWORD=elastic

# Password for the 'kibana_system' user (at least 6 characters)
KIBANA_PASSWORD=kibana

# Version of Elastic products
STACK_VERSION=8.6.2

# Set the cluster name
CLUSTER_NAME=docker-cluster

# Set to 'basic' or 'trial' to automatically start the 30-day trial
LICENSE=basic
#LICENSE=trial

# Port to expose Elasticsearch HTTP API to the host
ES_PORT=9200
#ES_PORT=127.0.0.1:9200

# Port to expose Kibana to the host
KIBANA_PORT=5601
#KIBANA_PORT=80

# Increase or decrease based on the available host memory (in bytes)
MEM_LIMIT=1073741824

# Project namespace (defaults to the current folder name if not set)
#COMPOSE_PROJECT_NAME=myproject

```

At the kibana download stage, I get the following error:

```auto
[2023-03-10T09:24:11.109+00:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. security_exception: [security_exception] Reason: unable to authenticate user [kibana_system] for REST request [/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip]

```

And there are such errors in the elasticsearch container:

```auto
{"@timestamp":"2023-03-10T09:25:53.605Z", "log.level":"ERROR", "message":"failed to retrieve password hash for reserved user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[es01][transport_worker][T#2]","log.logger":"org.elasticsearch.xpack.security.authc.esnative.ReservedRealm","trace.id":"6182cca2752e51bd81d2428a7a29c162","elasticsearch.cluster.uuid":"kiUrFIPdTKCDlKzo75K_VA","elasticsearch.node.id":"tK3ZqWc6T5qp18M-lqIEhw","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster","error.type":"org.elasticsearch.action.UnavailableShardsException","error.message":"at least one primary shard for the index [.security-7] is unavailable","error.stack_trace":"org.elasticsearch.action.UnavailableShardsException: at least one primary shard for the index [.security-7] is unavailable\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.support.SecurityIndexManager.getUnavailableReason(SecurityIndexManager.java:138)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.esnative.NativeUsersStore.getReservedUserInfo(NativeUsersStore.java:603)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.esnative.ReservedRealm.getUserInfo(ReservedRealm.java:275)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.esnative.ReservedRealm.doAuthenticate(ReservedRealm.java:135)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.support.CachingUsernamePasswordRealm.authenticateWithCache(CachingUsernamePasswordRealm.java:200)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.support.CachingUsernamePasswordRealm.authenticate(CachingUsernamePasswordRealm.java:105)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.RealmsAuthenticator.lambda$consumeToken$4(RealmsAuthenticator.java:147)\n\tat org.elasticsearch.xcore@8.6.2/org.elasticsearch.xpack.core.common.IteratingActionListener.run(IteratingActionListener.java:117)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.RealmsAuthenticator.consumeToken(RealmsAuthenticator.java:234)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.RealmsAuthenticator.authenticate(RealmsAuthenticator.java:83)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.lambda$getAuthenticatorConsumer$5(AuthenticatorChain.java:180)\n\tat org.elasticsearch.xcore@8.6.2/org.elasticsearch.xpack.core.common.IteratingActionListener.onResponse(IteratingActionListener.java:135)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.lambda$getAuthenticatorConsumer$5(AuthenticatorChain.java:158)\n\tat org.elasticsearch.xcore@8.6.2/org.elasticsearch.xpack.core.common.IteratingActionListener.onResponse(IteratingActionListener.java:135)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.lambda$getAuthenticatorConsumer$5(AuthenticatorChain.java:158)\n\tat org.elasticsearch.xcore@8.6.2/org.elasticsearch.xpack.core.common.IteratingActionListener.onResponse(IteratingActionListener.java:135)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.lambda$getAuthenticatorConsumer$5(AuthenticatorChain.java:158)\n\tat org.elasticsearch.xcore@8.6.2/org.elasticsearch.xpack.core.common.IteratingActionListener.run(IteratingActionListener.java:117)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.doAuthenticate(AuthenticatorChain.java:136)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticatorChain.authenticateAsync(AuthenticatorChain.java:95)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticationService.authenticate(AuthenticationService.java:149)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.authc.AuthenticationService.authenticate(AuthenticationService.java:127)\n\tat org.elasticsearch.security@8.6.2/org.elasticsearch.xpack.security.rest.SecurityRestFilter.handleRequest(SecurityRestFilter.java:101)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.rest.RestController.dispatchRequest(RestController.java:398)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.rest.RestController.tryAllHandlers(RestController.java:532)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.rest.RestController.dispatchRequest(RestController.java:313)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.http.AbstractHttpServerTransport.dispatchRequest(AbstractHttpServerTransport.java:379)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.http.AbstractHttpServerTransport.handleIncomingRequest(AbstractHttpServerTransport.java:460)\n\tat org.elasticsearch.server@8.6.2/org.elasticsearch.http.AbstractHttpServerTransport.incomingRequest(AbstractHttpServerTransport.java:353)\n\tat org.elasticsearch.transport.netty4@8.6.2/org.elasticsearch.http.netty4.Netty4HttpPipeliningHandler.handlePipelinedRequest(Netty4HttpPipeliningHandler.java:128)\n\tat org.elasticsearch.transport.netty4@8.6.2/org.elasticsearch.http.netty4.Netty4HttpPipeliningHandler.channelRead(Netty4HttpPipeliningHandler.java:118)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:336)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:308)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.handler@4.1.84.Final/io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1373)\n\tat io.netty.handler@4.1.84.Final/io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1236)\n\tat io.netty.handler@4.1.84.Final/io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1285)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:519)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:458)\n\tat io.netty.codec@4.1.84.Final/io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:280)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.nio.NioEventLoop.processSelectedKeysPlain(NioEventLoop.java:689)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:652)\n\tat io.netty.transport@4.1.84.Final/io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)\n\tat io.netty.common@4.1.84.Final/io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)\n\tat io.netty.common@4.1.84.Final/io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat java.base/java.lang.Thread.run(Thread.java:1589)\n"}
{"@timestamp":"2023-03-10T09:25:53.608Z", "log.level": "INFO", "message":"Authentication of [kibana_system] was terminated by realm [reserved] - failed to authenticate user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[es01][transport_worker][T#2]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","trace.id":"6182cca2752e51bd81d2428a7a29c162","elasticsearch.cluster.uuid":"kiUrFIPdTKCDlKzo75K_VA","elasticsearch.node.id":"tK3ZqWc6T5qp18M-lqIEhw","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster"}

```

If I do everything according to the instructions and it does not work, then what did I not take into account? Or is the instruction incorrect?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 10, 2023, 10:22am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/2 "2023-03-10T10:22:06Z")

</div>

Welcome!

What exact command line are you running? What is your `docker-compose.yml` file?

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 10:33am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/3 "2023-03-10T10:33:04Z")

</div>

I copied the example given [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html#docker-file) into my `docker-compose.yml`

![изображение](https://us1.discourse-cdn.com/elastic/original/3X/2/6/2686f43a5cc5494a73018dfa2054560d778b49e4.png)

Everything went well, but everything slows down on kibana authorization

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 10, 2023, 10:49am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/4 "2023-03-10T10:49:46Z")

</div>

Did you modify anything in that file?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 10, 2023, 11:03am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/5 "2023-03-10T11:03:40Z")

</div>

I just tested it locally and it's all good.

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 11:30am UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/6 "2023-03-10T11:30:52Z")

</div>

I recorded a [video](https://youtu.be/RH5362qPpDU) of starting the stack from the very beginning. I have Alpine Linux running on which I run. Docker works on it.

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 2:22pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/7 "2023-03-10T14:22:17Z")

</div>

Maybe I should look at some logs to see the reason?

---

<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, 2:55pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/8 "2023-03-10T14:55:31Z")

</div>

Hi @alexanderzhirov

There's also a kind of a subtle issue.

If you're just testing restarting etc, you should cleanup / delete the volumes because the volumes do not get deleted each time you run this and if they already exist.... they don't get written over. So if for some reason it didn't work the first time running it over and over typically won't fix it.

I've had several users running to this and it was very tricky to find.

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 3:08pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/9 "2023-03-10T15:08:10Z")

</div>

I delete volumes before starting. In the [video](https://www.youtube.com/watch?v=RH5362qPpDU) I demonstrated the launch on a clean docker. I have a feeling that docker does not read the set password from the `.env` file

---

<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:09pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/10 "2023-03-10T15:09:59Z")

</div>

Did you try with a simple password, perhaps you have a character that's having trouble being read (ohh I see simple).. ok I'll take a look at the video... The process works for me as well a couple days ago I will test again.

Oh @alexanderzhirov Welcome to the community....

---

<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"
}

```

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 3:55pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/12 "2023-03-10T15:55:14Z")

</div>

> [@stephenb](#):
>
> docker system prune -a

Damn, you were right! It was necessary to perform a complete cleaning. I have accumulated 5 gigabytes in my cache. After deleting the cache, everything worked out! Thank you very much! My inattention cost me a lesson. 😀

---

<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:57pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/13 "2023-03-10T15:57:59Z")

</div>

Yeah I have used docker a lot but I am not an expert... sometimes it is unclear to me what is left behind and what is not... lucky for me I can run a prune and start clean.

Cool enjoy...

Now what is interesting ... you should really may a copy of the compose without all the setup stuff ... because no need to run all that over and over... if that make sense.... it is really just meant as a startup example...

---

<div class="post-metadata">

**Author:** ![alexanderzhirov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexanderzhirov/32/118321_2.png) [@alexanderzhirov](https://discuss.elastic.co/u/alexanderzhirov)\
**Post date:** [March 10, 2023, 4:00pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/14 "2023-03-10T16:00:14Z")

</div>

I'm just trying to get acquainted with this stack through training examples 👨‍🎓

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 7, 2023, 4:00pm UTC](https://discuss.elastic.co/t/the-stack-cannot-be-started-according-to-the-instructions/327431/15 "2023-04-07T16:00:15Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.