Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

sysctl: error setting key 'vm.max_map_count': Read-only file system

See original GitHub issue

When I try to start elasticsearch-kibana only kibana pod is running and elasticsearch goes in Init Crash Loop Back-off.

I read the pod logs kubectl logs elasticsearch-7fc6f9b9bb-8ffgg --all-containers=true and this is the content sysctl: error setting key 'vm.max_map_count': Read-only file system Error from server (BadRequest): container "elasticsearch" in pod "elasticsearch-7fc6f9b9bb-8ffgg" is waiting to start: PodInitializing Any idea? thx

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:17 (8 by maintainers)

Top GitHub Comments

2reactions

sp1d3rinocommented, Apr 7, 2020

I solved.

from the host I ran sudo sysctl -w vm.max_map_count=262144
from the elk yaml I removed this line decommand: ['sysctl', '-w', 'vm.max_map_count=262144'] and I put privileged: false

deleted the elasticsearch deployment and applied one more time.

2reactions

hzhao-githubcommented, Apr 6, 2020

Hi sp1d3rino,

Can you please try to add the block below to your elk yaml file?

   spec:
  initContainers:
  - name: set-vm-max-map-count
    image: busybox
    imagePullPolicy: IfNotPresent
    command: ['sysctl', '-w', 'vm.max_map_count=262144']
    securityContext:
      privileged: true
  containers:
  - name: "elasticsearch"
  .....