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.
how can i connect to bash mode?
I am using the below to override entrypoint, but it doesn't work for me.
sudo docker run -it --entrypoint=/bin/bash -p 9000:9000 -p 9092:9092 sonarqube:5.6.7-alpine
There is no document mention why 9092 port needs to open. Could someone tell me what that port use for?
docker run --name sonarqube--postgresql -d --publish 35432:5432 --restart always --env POSTGRES_USER=sonar --env POSTGRES_PASSWORD=sonar --volume /docker/volumes/sonarqube/postgresql:/var/lib/postgresql --volume /docker/volumes/sonarqube/postgresql/data:/var/lib/postgresql/data postgres
docker run --name sonarqube -d --publish 9000:9000 -p 9092:9092 -e SONARQUBE_JDBC_USERNAME=sonar -e SONARQUBE_JDBC_PASSWORD=sonar -e 'SONARQUBE_JDBC_URL=jdbc:postgresql://cocreate-centos7.isee.mitre.org:35432/sonar' --volume /docker/volumes/sonarqube/conf:/opt/sonarqube/conf --volume /docker/volumes/sonarqube/data:/opt/sonarqube/data --volume /docker/volumes/sonarqube/extensions:/opt/sonarqube/extensions --volume /docker/volumes/sonarqube/lib/bundled-plugins:/opt/sonarqube/lib/bundled-plugins sonarqube
I can get it to run, but once you admin:admin and enter a token to be generate it immediately kicks you out to reauth with the error message, "The request cannot be processed. Try again later."
Official solution works on Linux containers only.
So, I ran SonarQube with MySQL on windows container: https://hub.docker.com/r/dnikolayev/sonarqube-mysql-windows/
Extensions are coming as Volume, so Updates and adding custom plugins are allowed.
If you have situation like I had with no Linux, but Windows 2016 Server - you're welcome!
RUN set -x \
&& curl -fSL -o sonar-findbugs-plugin.jar https://github.com/SonarQubeCommunity/sonar-findbugs/releases/download/3.5.0/sonar-findbugs-plugin.jar \
&& curl -fSL -o sonar-pmd-plugin.jar https://sonarsource.bintray.com/Distribution/sonar-pmd-plugin/sonar-pmd-plugin-2.5.jar \
&& curl -fSL -o sonar-timeline-plugin.jar http\://downloads.sonarsource.com/plugins/org/codehaus/sonar-plugins/sonar-timeline-plugin/1.5/sonar-timeline-plugin-1.5.jar
I'm trying to add plugins with a custom dockerfile:
RUN wget https://sonarsource.bintray.com/Distribution/sonar-java-plugin/sonar-java-plugin-220.127.116.1160.jar
RUN wget https://sonarsource.bintray.com/Distribution/sonar-scm-git-plugin/sonar-scm-git-plugin-1.2.jar
RUN wget https://sonarsource.bintray.com/Distribution/sonar-github-plugin/sonar-github-plugin-18.104.22.1682.jar
However, when I run a container I don't see these as installed in an instance. I suppose they must be registered somewhere in DB too.. I would appreciate if you add a note on how to customize this image with plugins
When is 6.4 in docker available?
If you have issues restarting because of permissions on /opt/sonarqube/temp/README.txt, try mounting /opt/sonarqube/temp as a volume on your container
Can we configure every settings using env ? (eg: SONAR_LOG_LEVEL=DEBUG)