[SOLVED] SonarQube Max virtual memory areas vm max_map_count 65530 is too low, increase to at least [262144]

You are currently viewing [SOLVED] SonarQube Max virtual memory areas vm max_map_count 65530 is too low, increase to at least [262144]
Photo by Stefan Widua on Unsplash
Share This Post, Help Others, And Earn My Heartfelt Appreciation! :)
4.8
(1385)

SonarQube is the tool which allows developers to keep the clean code in their repositories. [ SonarQube Max virtual memory areas vm max_map_count 65530 ] It do automatic check every time when new code is pushed to the repository. If you haven’t started using this tool yet, then start! It will pay you back in the future.

Problem -> SonarQube Max virtual memory areas vm max_map_count 65530

The system isn’t allowed to get the requested virtual memory amount.

In computing, virtual memory, or virtual storage[b] is a memory management technique that provides an “idealized abstraction of the storage resources that are actually available on a given machine”[3] which “creates the illusion to users of a very large (main) memory”

https://en.wikipedia.org/wiki/Virtual_memory

Solution

Run the following command before attempting to start Sonar or issuing your docker-compose command:

sudo sysctl -w vm.max_map_count=262144

max virtual memory areas vm.max_map_count 65530 is too low SonarQube

If you enjoyed this post please add the comment below and share this post on your Facebook, Twitter, LinkedIn or another social media webpage.
Thanks in advanced!

How useful was this post?

Click on a star to rate it!

Average rating 4.8 / 5. Vote count: 1385

No votes so far! Be the first to rate this post.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments