# How to bypass vm.max\_map\_count check upon start?

**URL:** <https://discuss.elastic.co/t/how-to-bypass-vm-max-map-count-check-upon-start/101354>\
**Category:** Elasticsearch\
**Created:** [September 21, 2017, 2:32pm UTC](https://discuss.elastic.co/t/how-to-bypass-vm-max-map-count-check-upon-start/101354 "2017-09-21T14:32:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![WoJ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/woj/32/4518_2.png) [@WoJ](https://discuss.elastic.co/u/WoJ)\
**Post date:** [September 21, 2017, 2:32pm UTC](https://discuss.elastic.co/t/how-to-bypass-vm-max-map-count-check-upon-start/101354/1 "2017-09-21T14:32:51Z")

</div>

Hello

I use Elasticsearch 5 in a container (`systemd-nspawn`) and when I attempt to start it, I get the error

```
max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

```

As mentionned in various places, the virtual memory should be set up to 262144+ **on the host** , which is the case for my host:

```
root@the-host:~# sysctl vm.max_map_count
vm.max_map_count = 262144

```

This setting is also seen as high by the guest (container)

```
root@the-container:~# sysctl vm.max_map_count
vm.max_map_count = 262144

```

It therefore looks like ES starting in a container does not assess the value of `vm.max_map_count` correctly (wild guessing). **Is there a way to bypass this check?**

---

<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:** [October 19, 2017, 2:33pm UTC](https://discuss.elastic.co/t/how-to-bypass-vm-max-map-count-check-upon-start/101354/2 "2017-10-19T14:33:31Z")

</div>

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