# Docker max virtual memory areas vm.max\_map\_count is too low,

**URL:** <https://discuss.elastic.co/t/docker-max-virtual-memory-areas-vm-max-map-count-is-too-low/221779>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [March 2, 2020, 9:49pm UTC](https://discuss.elastic.co/t/docker-max-virtual-memory-areas-vm-max-map-count-is-too-low/221779 "2020-03-02T21:49:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![IRQ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/irq/32/45225_2.png) [@IRQ](https://discuss.elastic.co/u/IRQ)\
**Post date:** [March 29, 2020, 5:52pm UTC](https://discuss.elastic.co/t/docker-max-virtual-memory-areas-vm-max-map-count-is-too-low/221779/2 "2020-03-29T17:52:42Z")

</div>

After several hours of googling and debugging I eventually managed to turn off production mode by setting "discovery.type" to the value "single-node". I did it wiht OpenShift Web Console but it does not matter.

As far as I understand default mode for this setting has some other value so elasticsearch still performs bootstrap checks and fails. Probably the same effect would have been setting cluster.name variable to empty value but I did not try.

---

_[View the full topic](https://discuss.elastic.co/t/docker-max-virtual-memory-areas-vm-max-map-count-is-too-low/221779)._