Docker datacenter edition deploy error

SonarQube Server / Community Build
1

Below are the console logs

2025-11-11 11:10:58.348 | 2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2025-11-11 11:10:58.441 | 2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch cluster enabled. Connect to hosts [search-1]
2025-11-11 11:10:58.442 | 2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 172.20.0.4:9001, TCP: 172.20.0.4:{}]
2025-11-11 11:10:58.629 | 2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/java/openjdk/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elasticsearch -Des.path.conf=/opt/sonarqube/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube/elasticsearch/lib/*:/opt/sonarqube/elasticsearch/lib/cli-launcher/* org.elasticsearch.launcher.CliToolLauncher
2025-11-11 11:10:58.824 | Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
2025-11-11 11:11:04.663 | java.lang.RuntimeException: starting java failed with [137]
2025-11-11 11:11:04.675 | output:
2025-11-11 11:11:04.675 | 
2025-11-11 11:11:04.675 | error:
2025-11-11 11:11:04.675 | 
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.JvmOption.flagsFinal(JvmOption.java:121)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.JvmOption.findFinalOptions(JvmOption.java:88)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.MachineDependentHeap.determineHeapSettings(MachineDependentHeap.java:56)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:146)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.JvmOptionsParser.determineJvmOptions(JvmOptionsParser.java:98)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.ServerCli.startServer(ServerCli.java:268)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.server.cli.ServerCli.execute(ServerCli.java:111)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.common.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:55)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:95)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.cli.Command.main(Command.java:52)
2025-11-11 11:11:04.675 | 	at org.elasticsearch.launcher.CliToolLauncher.main(CliToolLauncher.java:65)
2025-11-11 11:11:04.682 | 2025.11.11 03:11:04 WARN  search-1 app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 70
2025-11-11 11:11:04.682 | 2025.11.11 03:11:04 INFO  search-1 app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025-11-11 11:11:04.682 | 2025.11.11 03:11:04 INFO  search-1 app[][o.s.a.SchedulerImpl] SonarQube is stopped

Server logs

2025.11.11 03:07:22 INFO  search-1 app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2025.11.11 03:07:22 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch cluster enabled. Connect to hosts [search-1]
2025.11.11 03:07:22 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 172.20.0.4:9001, TCP: 172.20.0.4:{}]
2025.11.11 03:07:22 INFO  search-1 app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/java/openjdk/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elasticsearch -Des.path.conf=/opt/sonarqube/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube/elasticsearch/lib/*:/opt/sonarqube/elasticsearch/lib/cli-launcher/* org.elasticsearch.launcher.CliToolLauncher
2025.11.11 03:07:27 WARN  search-1 app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 70
2025.11.11 03:07:27 INFO  search-1 app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025.11.11 03:07:27 INFO  search-1 app[][o.s.a.SchedulerImpl] SonarQube is stopped
2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch cluster enabled. Connect to hosts [search-1]
2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 172.20.0.4:9001, TCP: 172.20.0.4:{}]
2025.11.11 03:10:58 INFO  search-1 app[][o.s.a.ProcessLauncherImpl] Launch process[ELASTICSEARCH] from [/opt/sonarqube/elasticsearch]: /opt/java/openjdk/bin/java -Xms4m -Xmx64m -XX:+UseSerialGC -Dcli.name=server -Dcli.script=./bin/elasticsearch -Dcli.libs=lib/tools/server-cli -Des.path.home=/opt/sonarqube/elasticsearch -Des.path.conf=/opt/sonarqube/temp/conf/es -Des.distribution.type=tar -cp /opt/sonarqube/elasticsearch/lib/*:/opt/sonarqube/elasticsearch/lib/cli-launcher/* org.elasticsearch.launcher.CliToolLauncher
2025.11.11 03:11:04 WARN  search-1 app[][o.s.a.p.AbstractManagedProcess] Process exited with exit value [ElasticSearch]: 70
2025.11.11 03:11:04 INFO  search-1 app[][o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2025.11.11 03:11:04 INFO  search-1 app[][o.s.a.SchedulerImpl] SonarQube is stopped
2

Hey there.

You should just need to boost the memory available to the Docker container.

3

I have removed the cpu and memory limit, i.e. allow unlimited use same as the host, but I still got the same error.

4

Are you still getting this exception in the logs?

Anyway you slice it, java failing with a 137 means it couldn’t allocate enough memory for the Java process.

How much memory does the host have overall?