Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with vm.max_map_count": Read-only file system #503

Open
hitokiri opened this issue Jan 24, 2021 · 1 comment
Open

Problem with vm.max_map_count": Read-only file system #503

hitokiri opened this issue Jan 24, 2021 · 1 comment
Labels

Comments

@hitokiri
Copy link

Hello, trying to resolve a problem with the memory assigned to JDK, when you try to change the variable with the command sysctl the system returns this message
sysctl: setting key "vm.max_map_count": Read-only file system

I Don't can resolve this problem, help me please, I have tried many forms

sysctl -w vm.max_map_count=262144

I use AMR64, which is a Raspberry 4

@bharathappali
Copy link
Collaborator

I'm not sure if it's the problem with openjdk-docker images, the setting your are trying will be changing the file /proc/sys/vm/max_map_count which is procfs, I feel docker mounts procfs as the read-only file system.

It cannot be set with --sysctl option of docker as it is a node-level sysctl.

Possible workarounds I can think of are [Just listing them but not recommended]:

  • Remounting procfs with read-write access by running container with --privileged
  • Setting vm.max_map_count on host as it gets reflected in the containers as well

@karianna karianna added the bug label Feb 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants