# Elasticsearch docker ulimit

**URL:** <https://discuss.elastic.co/t/elasticsearch-docker-ulimit/124157>\
**Category:** Elasticsearch\
**Created:** [March 15, 2018, 6:00pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-ulimit/124157 "2018-03-15T18:00:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fei\_Yao](https://avatars.discourse-cdn.com/v4/letter/f/85e7bf/32.png) [@Fei\_Yao](https://discuss.elastic.co/u/Fei_Yao)\
**Post date:** [March 15, 2018, 6:00pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-ulimit/124157/1 "2018-03-15T18:00:21Z")

</div>

first of all, my Elasticsearch docker (under unprivileged mode, and using office Elasticsearch docker image from [https://www.docker.elastic.co/](https://www.docker.elastic.co/)) has passed boostrap check by setting correct vm.max\_map\_count, etc. One thing really piqued my curiosity, which is ulimit.

1. inside the container I have:  
ulimit -n =\> 1048576  
ulimit -u =\> unlimited

2. outside the container, and at the VM level I have the following:  
ulimit -n =\> 1024  
ulimit -u =\> 31706

So, it is plausible container can override daemon ulimit without using privileged mode? In my scenario above, do you think it is production-ready?

According to [https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html). It appears I can do either at the VM level (docker daemon), or container level like below.

`--ulimit nofile=65536:65536`

Any advice?  
Thanks

---

<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 12, 2018, 6:00pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-ulimit/124157/2 "2018-04-12T18:00:40Z")

</div>

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