Memory error on upgrade

Hello, I am trying to upgrade our developer edition SonarQube from 9.7 to 9.9-LTS in docker but got the following error:

sonarqube | [0.002s][warning][os,thread] Failed to start thread “GC Thread#0” - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
sonarqube | #
sonarqube | # There is insufficient memory for the Java Runtime Environment to continue.

What should I do next? Thanks.

1 Like

Your docker host machine’s memory is not sufficient to run SonarQube container. Just raise host machine’s memory will be ok.

Thank you Jianbing.

I just checked the memory of the host:

total used free shared buff/cache available
Mem: 62Gi 40Gi 9.4Gi 201Mi 12Gi 21Gi
Swap: 975Mi 975Mi 0.0Ki

It looks like I have enough memory. Is there any other reason it might be? Thanks.

Figured out. Thanks.

Our Docker version was too low. Upgraded to the latest and now it works.

Hey Mike I’m facing the same thing - what version of Docker were you using and which version did you upgrade to?

Hi Mark,

We are running Docker version 23.0.1, build a5ee5b1 on Ubuntu 20.04.2 LTS.

I don’t remember the old Docker version. If you let me know how I can figure out I might give it a shot.

Good luck!

Thanks Mike. I’ll push for an upgrade to our preloaded Docker installation accordingly. We’ve been using a much older version…
I suspect the problem is related to DOCKER-111. I upgraded to 20.10.7 and am having other permissions-related issues now so there’s some progress at least.

Hey all.

As a heads-up, we’ve updated our Install the Server documentation to specify a Docker Engine version, and we should be updating our upgrade notes as well.

1 Like

Thank you for updating the documentation!

Hi, we’re also seeing this issue after upgrading from 8.9 to 9.9. However, we’re not using docker runtime, we’re using RHEL8 + containerd

Any advice on what we can do to resolve this?

Hi @Tony.Noble,

This thread is about running 9.9 on Docker - which we support.

Yours sounds like a new topic.


I faced the same issues on Ubuntu 16.04.7 LTS with Docker version 20.10.7 installed. I was able to resolve by invoking docker run with the parameters --security-opt seccomp=unconfined.