CODEWITHSUNDEEP
dockersonarqube
thepolina
thepolina

Reputation: 1274

SonarQube docker container can't start, elasticsearch issue

I'm trying to run official SonarQube Docker container locally. I'm using the command provided here: https://hub.docker.com/_/sonarqube/

It exits about 1 minute after it was started. Logs are reporting Elasticsearch connectivity issue

2017.09.05 08:16:40 INFO  web[][o.e.client.transport] [Edwin Jarvis] failed to connect to node [{#transport#-1}{127.0.0.1}{127.0.0.1:9001}], removed from nodes list
org.elasticsearch.transport.ConnectTransportException: [][127.0.0.1:9001] connect_timeout[30s]
.....
Caused by: java.net.ConnectException: Connection refused: /127.0.0.1:9001
.....
    ... 3 common frames omitted
2017.09.05 08:17:10 INFO  app[][o.s.a.SchedulerImpl] Process [web] is stopped
2017.09.05 08:17:10 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped

Upvotes: 0

Views: 3413

Answers (3)

novice_coder99
novice_coder99

Reputation: 1

At host machine i ran below command and started the container and it worked for me

In /etc/sysctl.conf vm.max_map_count=262144 save and exit and run below command sudo sysctl -p

Upvotes: 0

Rahul Reghunath
Rahul Reghunath

Reputation: 1276

for me it was the because of the system setting vm.max_map_count

the value should be a minimum of 262144. More details in the documentation

in Linux machine, the configuration can be added in the file /etc/sysctl.conf

Upvotes: 0

thepolina
thepolina

Reputation: 1274

Turns out SonarQube container didn't have enough resources. I shut down other docker containers and it works for me now.

Upvotes: 4

Related Questions