Official Repository

Last pushed: a day ago
Short Description
SonarQube is an open source platform for continuous inspection of code quality.
Full Description

Supported tags and respective Dockerfile links

For more information about this image and its history, please see the relevant manifest file (library/sonarqube). This image is updated via pull requests to the docker-library/official-images GitHub repo.

For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the repos/sonarqube/tag-details.md file in the docker-library/repo-info GitHub repo.

What is SonarQube?

SonarQube is an open source platform for continuous inspection of code quality.

wikipedia.org/wiki/SonarQube

How to use this image

Run SonarQube

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"

Database configuration

By default, the image will use an embedded H2 database that is not suited for production.

The production database is configured with these variables: SONARQUBE_JDBC_USERNAME, SONARQUBE_JDBC_PASSWORD and SONARQUBE_JDBC_URL.

$ 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.

Administration

The administration guide can be found here.

Image Variants

The sonarqube images come in many flavors, each designed for a specific use case.

sonarqube:<version>

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.

sonarqube:alpine

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 git or 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).

License

View license information for the software contained in this image.

Supported Docker versions

This image is officially supported on Docker version 17.03.0-ce.

Support for older versions (down to 1.6) is provided on a best-effort basis.

Please see the Docker installation documentation for details on how to upgrade your Docker daemon.

User Feedback

Issues

If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a cve-tracker issue on the official-images repository first.

You can also reach many of the official image maintainers via the #docker-library IRC channel on Freenode.

Contributing

You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.

Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.

Documentation

Documentation for this image is stored in the sonarqube/ directory of the docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's README.md file before attempting a pull request.

Docker Pull Command

Comments (24)
robertjebakumar
2 months ago

Hi Team, Does this image already have sonar-scanner bundled with it, if not what is the method to do it

ebuildy
4 months ago

It's not provide "sonar-scanner" ?

chw717
5 months ago

JDBC URL must have the property 'characterEncoding=utf8'

ovelindstrom
6 months ago

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.

derekhsu
8 months ago

I add volume on $SONARQUBE_HOME/conf and create a new image my own because I have to add LDAP configuration.

zinkevich
8 months ago

Hi,
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

gzockoll
9 months ago

My solution for adding plugins is here: https://github.com/MehrCurry/docker-sonar

mgeeves
10 months ago

There may be a better way than this, but for running behind an apache frontend (ProxyPass to /sonar), I needed to change the entrypoint in the docker-compose example:

entrypoint:

  • ./bin/run.sh
  • -Dsonar.web.context=/sonar
bobbywhitesfdc
10 months ago

It would be super nice if you could include a recipe / "how to" for adding a plugin.

mbuchner
a year ago

Could you also expose ""$SONARQUBE_HOME/conf", "$SONARQUBE_HOME/data"" as volumes. Conf is required to configure e.g. LDAP or create a way to make all this settings via ENV!?