Container vm.max_map_count Error

Summary

Intermittent errors about virtual memory areas too low.

Steps to reproduce

Start elasticsearch container to run elasticsearch, eg: install helm chart using 7.10.0 image.

What is the current bug behavior?

Container error-ing and exiting.

What is the expected correct behavior?

Elasticsearch starts, container shows 1/1 Ready and Elasticsearch is running.

Relevant logs and/or screenshots

{"type": "server", "timestamp": "2021-03-22T21:15:36,466Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "initialized" }
{"type": "server", "timestamp": "2021-03-22T21:15:36,466Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "starting ..." }
{"type": "server", "timestamp": "2021-03-22T21:15:36,605Z", "level": "INFO", "component": "o.e.t.TransportService", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "publish_address {10.42.0.11:9300}, bound_addresses {[::]:9300}" }
{"type": "server", "timestamp": "2021-03-22T21:15:36,810Z", "level": "INFO", "component": "o.e.b.BootstrapChecks", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "bound or publishing to a non-loopback address, enforcing bootstrap checks" }

ERROR: [1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/elasticsearch-kibana.log
{"type": "server", "timestamp": "2021-03-22T21:15:36,819Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "stopping ..." }
{"type": "server", "timestamp": "2021-03-22T21:15:36,837Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "stopped" }
{"type": "server", "timestamp": "2021-03-22T21:15:36,837Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "closing ..." }
{"type": "server", "timestamp": "2021-03-22T21:15:36,854Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "elasticsearch-kibana", "node.name": "elasticsearch-kibana-es-data-0", "message": "closed" }

Possible fixes

/etc/sysctl.conf inside the container

Defintion of Done

Bug has been identified and corrected within the container

/cc @ironbank-notifications/bug

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

Admin message