# Install ES Docker Compose

**URL:** <https://discuss.elastic.co/t/install-es-docker-compose/159268>\
**Category:** Elasticsearch\
**Created:** [December 4, 2018, 1:26am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268 "2018-12-04T01:26:42Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![diagriyanto](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@diagriyanto](https://discuss.elastic.co/u/diagriyanto)\
**Post date:** [December 4, 2018, 1:26am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/1 "2018-12-04T01:26:42Z")

</div>

hello, i'm new here and i want to ask something.

i've install ES using docker compose with tutorial on the docs. but the container won't run status exited and i found message like this .

> [root@s1 ~]# docker ps -a  
> CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
> 44600ac939ca [docker.elastic.co/elasticsearch/elasticsearch:6.5.1](http://docker.elastic.co/elasticsearch/elasticsearch:6.5.1) "/usr/local/bin/dock…" About a minute ago Exited (137) About a minute ago elasticsearch  
> bf50d8d7c0bb [docker.elastic.co/elasticsearch/elasticsearch:6.5.1](http://docker.elastic.co/elasticsearch/elasticsearch:6.5.1) "/usr/local/bin/dock…" About a minute ago Exited (137) About a minute ago elasticsearch2  
> [root@s1 ~]# docker logs elasticsearch  
> OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.  
> OpenJDK 64-Bit Server VM warning: UseAVX=2 is not supported on this CPU, setting it to UseAVX=1

what suppose i'm to do with this?

thanks!

---

<div class="post-metadata">

**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\
**Post date:** [December 5, 2018, 12:03am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/2 "2018-12-05T00:03:55Z")

</div>

Hi,

Let me ask a few questions to see if we can figure out what's going on:

Is that the complete log?  
Does the container have access to enough memory?  
Are you running this in a virtual machine (ie. are you using Windows or MacOS?).  
What documentation, specifically, are you reading?

Thanks.

---

<div class="post-metadata">

**Author:** ![diagriyanto](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@diagriyanto](https://discuss.elastic.co/u/diagriyanto)\
**Post date:** [December 5, 2018, 4:05am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/3 "2018-12-05T04:05:31Z")

</div>

hi,

-maybe ... yes, it's the log but not complete log..  
-around 1GB, is it okay?  
-i use VM with CENTOS 7 and install docker to it .  
-i read directly from docs of docker elasticsearch

thanks for your reply

---

<div class="post-metadata">

**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\
**Post date:** [December 5, 2018, 5:16am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/4 "2018-12-05T05:16:37Z")

</div>

1GB? That's probably not enough.

Exit code 137 means that somebody sent `SIGKILL` to Elasticsearch. It was probably the [OOM Killer](https://www.kernel.org/doc/gorman/html/understand/understand016.html).

EDIT: Check the output of `dmesg` for evidence of the OOM killer in action.

---

<div class="post-metadata">

**Author:** ![diagriyanto](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@diagriyanto](https://discuss.elastic.co/u/diagriyanto)\
**Post date:** [December 6, 2018, 5:24am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/5 "2018-12-06T05:24:02Z")

</div>

oh boy,  
so what minimum requirement for docker elastic? 2GB ? or more?

sorry, cus docker container status has exited.. i cant dmesg it.

---

<div class="post-metadata">

**Author:** ![jarpy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jarpy/32/51290_2.png) [@jarpy](https://discuss.elastic.co/u/jarpy)\
**Post date:** [December 6, 2018, 6:27am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/6 "2018-12-06T06:27:55Z")

</div>

`dmesg` operates on the kernel so it doesn't mind that the container process has died. Just run it on the host.

2GB is a better bet. You could also try tuning the heap size down if you're just experimenting.

[https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/heap-size.html)

---

<div class="post-metadata">

**Author:** ![diagriyanto](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@diagriyanto](https://discuss.elastic.co/u/diagriyanto)\
**Post date:** [December 6, 2018, 6:45am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/7 "2018-12-06T06:45:53Z")

</div>

ohh.. i see i see .

maybe i want to try it first ..

thank you for the advice !! sorry if i ask again if i found an error 😄

---

<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 3, 2019, 6:45am UTC](https://discuss.elastic.co/t/install-es-docker-compose/159268/8 "2019-01-03T06:45:54Z")

</div>

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