WARNING overcommit_memory is set to 0

[nimf]

When I start container, I see this in logs:

WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

I want data to be persistent. Should I worry about it?

[yosifkit]

Not being a big redis user I am not sure on the implications of this setting, but you can provide your own redis.conf (see the redis doc on the Docker hub).

[abunimeh]

The short answer to your question is No.

If you think you application is going to use a lot of memory. i.e. more than your RAM then set this to 1.
You cannot set this using redis.conf like @yosifkit said.

[nimf]

Ok, thank you.

[bkuhl]

This isn't a "run a container to solve a problem" kind of thing, but I appreciate there being containers running as part of a stack to help serve as documentation for what's been done to the host. That said, I believe some folks may find https://github.com/bkuhl/redis-overcommit-on-host useful.