# Elasticsearch in Docker--a good idea?

**URL:** <https://discuss.elastic.co/t/elasticsearch-in-docker-a-good-idea/126234>\
**Category:** Elasticsearch\
**Created:** [March 30, 2018, 1:29pm UTC](https://discuss.elastic.co/t/elasticsearch-in-docker-a-good-idea/126234 "2018-03-30T13:29:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hokiegeek2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hokiegeek2/32/11076_2.png) [@hokiegeek2](https://discuss.elastic.co/u/hokiegeek2)\
**Post date:** [March 30, 2018, 1:29pm UTC](https://discuss.elastic.co/t/elasticsearch-in-docker-a-good-idea/126234/1 "2018-03-30T13:29:37Z")

</div>

Hi Everyone,

I am currently researching an issue I am seeing in my Elasticsearch Docker on Mesos/Marathon whereby it _appears_ that Lucene is slowly grabbing more and more off-heap memory (page cache) until it exceeds the max memory configured for Mesos and then Mesos kills the container (exit status 137).

Question--is anyone else running Elasticsearch in Docker containers in production? If so, are you seeing what I am describing here, and, if so, what did you do to solve the issue?

Any feedback is greatly appreciated.

Thanks

--John

---

<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 27, 2018, 1:29pm UTC](https://discuss.elastic.co/t/elasticsearch-in-docker-a-good-idea/126234/2 "2018-04-27T13:29:48Z")

</div>

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