-
Notifications
You must be signed in to change notification settings - Fork 0
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
setting key "vm.overcommit_memory": Read-only file system #1
Comments
Thanks for the heads up, I am taking a look at the cause. |
It appears that This leaves three options.
I will update the README to note this limitation. |
Enabling sysctl vm.overcommit_memory=1 on the docker host will NOT be inherited by the running containers :-( EDIT1: Yes it will inherit. |
Hey, folks. Has anyone solved this issue? |
anyone at all? |
I checked with Docker 17.03.1-ce today and option #1 I mentioned above seems to work on Ubuntu 14.04.5 LTS host: host# sysctl vm.overcommit_memory
vm.overcommit_memory = 0
host# docker run -it --rm openfirmware/redis sysctl vm.overcommit_memory
vm.overcommit_memory = 0
host# sysctl vm.overcommit_memory=1
vm.overcommit_memory = 1
host# sysctl vm.overcommit_memory
vm.overcommit_memory = 0
host# docker run -it --rm openfirmware/redis sysctl vm.overcommit_memory
vm.overcommit_memory = 1 Option #2 doesn't work for me though. Let me know if that doesn't work for you. |
see redis/docker-library-redis#19
The text was updated successfully, but these errors were encountered: