# Elasticsearch exited with code 0

**URL:** <https://discuss.elastic.co/t/elasticsearch-exited-with-code-0/212131>\
**Category:** Elasticsearch\
**Created:** [December 17, 2019, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-exited-with-code-0/212131 "2019-12-17T09:58:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jporter](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jporter](https://discuss.elastic.co/u/jporter)\
**Post date:** [December 17, 2019, 9:58am UTC](https://discuss.elastic.co/t/elasticsearch-exited-with-code-0/212131/1 "2019-12-17T09:58:59Z")

</div>

I came in yesterday morning, and my elasticsearch would no longer start. I have checked my docker preferrences on my mac running OS X version 10.14.6 memory allocation is set to 4GiB (and I fiddled with this just to be sure this wasn't having any impact) my laptop's RAM is 16GB.

Convinced it wasn't my docker-compose.yml, but willing to try all the same (because I know it was working friday), I have copied the docker-compose.yml off the example page with no changes in observed output [https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html)

If I check docker-stats my memory usage for other containers is zero as I have shut them all off in debugging this issue.

As far as I understand, exit code 0 is not an error code but just indicates that a process has finished - is there a way I can see why elasticsearch believes it is complete? As I believe by default it should run forever

```
server jporter$ docker-compose up
Starting es03 ... done
Starting es02 ... done
Starting es01 ... done
Attaching to es03, es02, es01
es03 exited with code 0
es02 exited with code 0
es01 exited with code 0
```

---

<div class="post-metadata">

**Author:** ![jporter](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@jporter](https://discuss.elastic.co/u/jporter)\
**Post date:** [December 17, 2019, 11:14am UTC](https://discuss.elastic.co/t/elasticsearch-exited-with-code-0/212131/2 "2019-12-17T11:14:02Z")

</div>

This appears to have been a Docker for mac issue. Restoring to factory settings fixed it

---

<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:** [January 14, 2020, 11:14am UTC](https://discuss.elastic.co/t/elasticsearch-exited-with-code-0/212131/3 "2020-01-14T11:14:15Z")

</div>

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