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

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

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 17 (8 by maintainers)

Most upvoted comments

I am on macOS and i cant do sudo sysctl -w vm.max_map_count=262144, even the solution on docker on mac here is not working for me (says tty file not found) I am running on docker engine v19.03.13 and Catalina 10.15.7 if anyone could help

y-tee on Nov 3, 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.

sp1d3rino on Apr 7, 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"
  .....

hzhao-github on Apr 6, 2020

looks like elastic search related, did you try to resolve following this solution: https://github.com/spujadas/elk-docker/issues/99

marinakog on Apr 6, 2020