Max virtual memory areas limit not being detected in Docker container despite being updated

Community
1

In the web console, I get the following warning:

Warning: vm.max_map_count limit is too low [current=262144, recommended=1048576]

I followed the steps outlined at Capacity planning | QuestDB and still run into this issue.

I’m on Fedora 40 Ultramarine and running QuestDB in a Docker container and cat /proc/sys/vm/max_map_count shows 1048576. I tried increasing it to 5242880 to no avail either.

I changed the setting, deleted the container, restarted the Docker service, and created a new container but it’s still reading the old value. I tried passing this value in via docker run --sysctl vm.max_map_count=1048576 image but this didn’t let me start the container either. What might be going wrong here?

2

Hi @ajaypillay ,

This is strange. It is difficult to get this working on MacOS, but usually it works on Linux i.e Ubuntu.

Unfortunately, I don’t believe docker run --sysctl supports that setting.

Others have encountered a similar issue in the past running ElasticSearch: https://stackoverflow.com/questions/5144584d6/elasticsearch-max-virtual-memory-areas-vm-max-map-count-65530-is-too-low-inc

I will see what I can find out about this stickiness issue.