Supported tags and respective
Where to file issues:
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is SonarQube?
SonarQube is an open source platform for continuous inspection of code quality.
How to use this image
The server is started this way:
$ docker run -d --name sonarqube -p 9000:9000 -p 9092:9092 sonarqube
To analyse a project:
$ On Linux: mvn sonar:sonar $ With boot2docker: mvn sonar:sonar -Dsonar.host.url=http://$(boot2docker ip):9000 -Dsonar.jdbc.url="jdbc:h2:tcp://$(boot2docker ip)/sonar"
By default, the image will use an embedded H2 database that is not suited for production.
The production database is configured with these variables:
$ docker run -d --name sonarqube \ -p 9000:9000 -p 9092:9092 \ -e SONARQUBE_JDBC_USERNAME=sonar \ -e SONARQUBE_JDBC_PASSWORD=sonar \ -e SONARQUBE_JDBC_URL=jdbc:postgresql://localhost/sonar \ sonarqube
More recipes can be found here.
The administration guide can be found here.
sonarqube images come in many flavors, each designed for a specific use case.
This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.
This image is based on the popular Alpine Linux project, available in the
alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.
This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn't have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.
To minimize image size, it's uncommon for additional related tools (such as
bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the
alpine image description for examples of how to install packages if you are unfamiliar).
View license information for the software contained in this image.
I found a workaround. You are not able to change the permissions on /opt/sonarqube/temp/README.txt as its all ??????'s. But you CAN
touch it, which will fix the permissions long enough for you to restart. They will however be reset after the restart.
It sounds like I'm having the same issue as @pachilo. I have tried all versions of the image and all fail after trigger restart.
Cleaning or creating temp directory /opt/sonarqube/temp
Exception in thread "Restartor 0" java.lang.RuntimeException: Failed to reset file system
Caused by: java.nio.file.NoSuchFileException: /opt/sonarqube/temp/README.txt
... 3 more
Can we configure every settings using env ? (eg: SONAR_LOG_LEVEL=DEBUG)
Hi Team. I'm noticing that there is a corrupt file in this image, more specifically in: /opt/sonarqube/temp/README.txt
This is causing SonarQube to fail to restart by itself, requiring a manual container shutdown.
Hi Team, Does this image already have sonar-scanner bundled with it, if not what is the method to do it
It's not provide "sonar-scanner" ?
JDBC URL must have the property 'characterEncoding=utf8'
Quite some time now since the DB-connection was removed...
[WARNING] Property 'sonar.jdbc.url' is not supported any more. It will be ignored. There is no longer any DB connection to the SQ database.
while trying to send report to sonar through MSBuild runner, the process fails at the "end" command being unable to request "api/ce/submit" service. Is this the problem with JRuby 1.7.19? How can this be fixed with Docker image? I can't update /opt/sonarqube/lib/server folder as it's not the volume