public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-17 13:41:30 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/sonarqube] Release 26.3.0-debian-12-r0 (#91218)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-03-03 13:08:33 +01:00
committed by GitHub
parent 5451179aae
commit 6314059658
2 changed files with 16 additions and 242 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/sonarqube/26/debian-12/Dockerfile
+7 -6
View File
@@ -8,13 +8,13 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-02-19T04:53:30Z" \
org.opencontainers.image.created="2026-03-03T11:17:01Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/sonarqube/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/sonarqube" \
org.opencontainers.image.title="sonarqube" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="26.2.0"
org.opencontainers.image.version="26.3.0"
ENV HOME="/" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -29,9 +29,9 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"postgresql-client-18.2.0-0-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"java-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \
"sonarqube-26.2.0-0-linux-${OS_ARCH}-debian-12" \
"sonarqube-26.3.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -50,10 +50,11 @@ RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs /
RUN /opt/bitnami/scripts/java/postunpack.sh
RUN /opt/bitnami/scripts/sonarqube/postunpack.sh
ENV APP_VERSION="26.2.0" \
ENV APP_VERSION="26.3.0" \
BITNAMI_APP_NAME="sonarqube" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/postgresql/bin:/opt/bitnami/java/bin:$PATH"
EXPOSE 9000
bitnami/sonarqube/README.md
+9 -236
View File
@@ -1,7 +1,5 @@
# Bitnami Secure Image for SonarQube&trade;
## What is SonarQube&trade;?
> SonarQube&trade; is an open source quality management platform that analyzes and measures code's technical quality. It enables developers to detect code issues, vulnerabilities, and bugs in early stages.
[Overview of SonarQube&trade;](https://www.sonarqube.org)
@@ -66,56 +64,10 @@ docker build -t bitnami/APP:latest .
SonarQube&trade; requires access to a PostgreSQL database to store information. We'll use the [Bitnami Docker Image for PostgreSQL](https://github.com/bitnami/containers/tree/main/bitnami/postgresql) for the database requirements.
### Using the Docker Command Line
#### Step 1: Create a network
```console
docker network create sonarqube-network
```
#### Step 2: Create a volume for PostgreSQL persistence and create a PostgreSQL container
```console
$ docker volume create --name postgresql_data
docker run -d --name postgresql \
--env ALLOW_EMPTY_PASSWORD=yes \
--env POSTGRESQL_USERNAME=bn_sonarqube \
--env POSTGRESQL_PASSWORD=bitnami \
--env POSTGRESQL_DATABASE=bitnami_sonarqube \
--network sonarqube-network \
--volume postgresql_data:/bitnami/postgresql \
bitnami/postgresql:latest
```
#### Step 3: Create volumes for SonarQube&trade; persistence and launch the container
```console
$ docker volume create --name sonarqube_data
docker run -d --name sonarqube \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env SONARQUBE_DATABASE_USER=bn_sonarqube \
--env SONARQUBE_DATABASE_PASSWORD=bitnami \
--env SONARQUBE_DATABASE_NAME=bitnami_sonarqube \
--network sonarqube-network \
--volume sonarqube_data:/bitnami/sonarqube \
bitnami/sonarqube:latest
```
Access your application at `http://your-ip/`
### Run the application using Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/sonarqube/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/apache).
If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md).
## Persisting your application
If you remove the container all your data will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@@ -126,71 +78,16 @@ The above examples define the Docker volumes named `postgresql_data` and `sonarq
To avoid inadvertent removal of volumes, you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
### Mount host directories as data volumes with Docker Compose
This requires a minor change to the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/sonarqube/docker-compose.yml) file present in this repository:
```diff
postgresql:
...
volumes:
- - postgresql_data:/bitnami/postgresql
+ - /path/to/postgresql-persistence:/bitnami/postgresql
...
sonarqube:
...
volumes:
- - sonarqube_data:/bitnami/sonarqube
+ - /path/to/sonarqube-persistence:/bitnami/sonarqube
...
-volumes:
- postgresql_data:
- driver: local
- sonarqube_data:
- driver: local
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
### Mount host directories as data volumes using the Docker command line
#### Step 1: Create a network (if it does not exist)
```console
docker network create sonarqube-network
```
#### Step 2. Create a PostgreSQL container with host volume
```console
docker run -d --name postgresql \
--env ALLOW_EMPTY_PASSWORD=yes \
--env POSTGRESQL_USERNAME=bn_sonarqube \
--env POSTGRESQL_PASSWORD=bitnami \
--env POSTGRESQL_DATABASE=bitnami_sonarqube \
--network sonarqube-network \
--volume /path/to/postgresql-persistence:/bitnami/postgresql \
bitnami/postgresql:latest
```
#### Step 3. Create the SonarQube&trade; container with host volumes
```console
docker run -d --name sonarqube \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env SONARQUBE_DATABASE_USER=bn_sonarqube \
--env SONARQUBE_DATABASE_PASSWORD=bitnami \
--env SONARQUBE_DATABASE_NAME=bitnami_sonarqube \
--network sonarqube-network \
--volume /path/to/sonarqube-persistence:/bitnami/sonarqube \
bitnami/sonarqube:latest
```
> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.
## Configuration
The following section describes the supported environment variables
### Environment variables
The following tables list the main variables you can set.
#### Customizable environment variables
| Name | Description | Default Value |
@@ -243,101 +140,17 @@ docker run -d --name sonarqube \
| `SONARQUBE_WEB_JAVA_ADD_OPTS` | Additional Java options for Web. | `${SONARQUBE_WEB_JAVA_ADD_OPTS:-} ${JAVA_TOOL_OPTIONS:-}` |
| `SONARQUBE_DEFAULT_DATABASE_HOST` | Default database server host. | `postgresql` |
When you start the SonarQube&trade; image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line. If you want to add a new environment variable:
- For docker-compose add the variable name and value under the application section in the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/sonarqube/docker-compose.yml) file present in this repository:
```yaml
sonarqube:
...
environment:
- SONARQUBE_PASSWORD=my_password
...
```
- For manual execution add a `--env` option with each variable and value:
```console
$ docker run -d --name sonarqube -p 80:8080 -p 443:8443 \
--env SONARQUBE_PASSWORD=my_password \
--network sonarqube-tier \
--volume /path/to/sonarqube-persistence:/bitnami \
bitnami/sonarqube:latest
```
When you start the SonarQube&trade; image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
### Examples
#### SMTP configuration using a Gmail account
#### SMTP configuration
This would be an example of SMTP configuration using a Gmail account:
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/sonarqube/docker-compose.yml) file present in this repository:
```yaml
sonarqube:
...
environment:
- SONARQUBE_DATABASE_USER=bn_sonarqube
- SONARQUBE_DATABASE_NAME=bitnami_sonarqube
- ALLOW_EMPTY_PASSWORD=yes
- SONARQUBE_SMTP_HOST=smtp.gmail.com
- SONARQUBE_SMTP_PORT_NUMBER=587
- SONARQUBE_SMTP_USER=your_email@gmail.com
- SONARQUBE_SMTP_PASSWORD=your_password
...
```
- For manual execution:
```console
$ docker run -d --name sonarqube -p 80:8080 -p 443:8443 \
--env SONARQUBE_DATABASE_USER=bn_sonarqube \
--env SONARQUBE_DATABASE_NAME=bitnami_sonarqube \
--env SONARQUBE_SMTP_HOST=smtp.gmail.com \
--env SONARQUBE_SMTP_PORT_NUMBER=587 \
--env SONARQUBE_SMTP_USER=your_email@gmail.com \
--env SONARQUBE_SMTP_PASSWORD=your_password \
--network sonarqube-tier \
--volume /path/to/sonarqube-persistence:/bitnami \
bitnami/sonarqube:latest
```
The `SONARQUBE_SMTP_*` environment variables allows you configure the SMTP settings in the application. Please take a look at the environment variables information above for more information.
#### Connect SonarQube&trade; container to an existing database
The Bitnami SonarQube&trade; container supports connecting the SonarQube&trade; application to an external database. This would be an example of using an external database for SonarQube&trade;.
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/sonarqube/docker-compose.yml) file present in this repository:
```diff
sonarqube:
...
environment:
- - SONARQUBE_DATABASE_HOST=mariadb
+ - SONARQUBE_DATABASE_HOST=mariadb_host
- SONARQUBE_DATABASE_PORT_NUMBER=3306
- SONARQUBE_DATABASE_NAME=sonarqube_db
- SONARQUBE_DATABASE_USER=sonarqube_user
- - ALLOW_EMPTY_PASSWORD=yes
+ - SONARQUBE_DATABASE_PASSWORD=sonarqube_password
...
```
- For manual execution:
```console
$ docker run -d --name sonarqube\
-p 8080:8080 -p 8443:8443 \
--network sonarqube-network \
--env SONARQUBE_DATABASE_HOST=mariadb_host \
--env SONARQUBE_DATABASE_PORT_NUMBER=3306 \
--env SONARQUBE_DATABASE_NAME=sonarqube_db \
--env SONARQUBE_DATABASE_USER=sonarqube_user \
--env SONARQUBE_DATABASE_PASSWORD=sonarqube_password \
--volume sonarqube_data:/bitnami/sonarqube \
bitnami/sonarqube:latest
```
In case the database already contains data from a previous SonarQube&trade; installation, you need to set the variable `SONARQUBE_SKIP_BOOTSTRAP` to `yes`. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting `SONARQUBE_SKIP_BOOTSTRAP` to `yes`, values for environment variables such as `SONARQUBE_USERNAME`, `SONARQUBE_PASSWORD` or `SONARQUBE_EMAIL` will be ignored.
The Bitnami SonarQube&trade; container supports connecting the SonarQube&trade; application to an external database. In case the database already contains data from a previous SonarQube&trade; installation, you need to set the variable `SONARQUBE_SKIP_BOOTSTRAP` to `yes`. Otherwise, the container would execute the installation wizard and could modify the existing data in the database. Note that, when setting `SONARQUBE_SKIP_BOOTSTRAP` to `yes`, values for environment variables such as `SONARQUBE_USERNAME`, `SONARQUBE_PASSWORD` or `SONARQUBE_EMAIL` will be ignored.
### FIPS configuration in Bitnami Secure Images
@@ -412,46 +225,6 @@ For the SonarQube&trade; container:
bitnami/sonarqube:latest
```
### Upgrade this image
Bitnami provides up-to-date versions of PostgreSQL and SonarQube&trade;, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the SonarQube&trade; container. For the PostgreSQL upgrade see: <https://github.com/bitnami/containers/tree/main/bitnami/postgresql#user-content-upgrade-this-image>
The `bitnami/sonarqube:latest` tag always points to the most recent release. To get the most recent release you can simple repull the `latest` tag from the Docker Hub with `docker pull bitnami/sonarqube:latest`. However it is recommended to use [tagged versions](https://hub.docker.com/r/bitnami/sonarqube/tags/).
#### Step 1: Get the updated image
```console
docker pull bitnami/sonarqube:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker-compose stop sonarqube
```
#### Step 3: Take a snapshot of the application state
Follow the steps in [Backing up your container](#backing-up-your-container) to take a snapshot of the current application state.
#### Step 4: Remove the currently running container
Remove the currently running container by executing the following command:
```console
docker-compose rm -v sonarqube
```
#### Step 5: Run the new image
Update the image tag in `docker-compose.yml` and re-create your container with the new image:
```console
docker-compose up -d
```
## Notable Changes
### 9.0.0-debian-10-r0