public_git
/
bitnami-containers
mirror of https://github.com/bitnami/containers.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[bitnami/sonarqube] Release 26.4.0-debian-12-r1 (#93067) 

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot 2026-05-12 00:26:41 +02:00 committed by GitHub
parent e474cc743b
commit e5164d44f2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 13 additions and 70 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/sonarqube/26/debian-12/Dockerfile
View File

@ -8,7 +8,7 @@ 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-04-10T15:33:59Z" \
org.opencontainers.image.created="2026-05-11T20:11:06Z" \
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" \
@ -30,7 +30,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \
"java-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \
"java-21.0.11-11-2-linux-${OS_ARCH}-debian-12" \
"sonarqube-26.4.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
@ -52,7 +52,7 @@ RUN /opt/bitnami/scripts/java/postunpack.sh
RUN /opt/bitnami/scripts/sonarqube/postunpack.sh
ENV APP_VERSION="26.4.0" \
BITNAMI_APP_NAME="sonarqube" \
IMAGE_REVISION="0" \
IMAGE_REVISION="1" \
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"

77
bitnami/sonarqube/README.md
View File

@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name sonarqube bitnami/sonarqube:latest
```
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/sonarqube/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/sonarqube/docker-compose.yml)
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/sonarqube).
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@ -120,8 +128,6 @@ The following tables list the main variables you can set.
| `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.
### Examples
#### SMTP configuration
@ -141,70 +147,7 @@ The Bitnami SonarQube&trade; Docker image from the [Bitnami Secure Images](https
## Logging
The Bitnami SonarQube&trade; Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs sonarqube
```
Or using Docker Compose:
```console
docker-compose logs sonarqube
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Maintenance
### Backing up your container
To backup your data, configuration and logs, follow these simple steps:
#### Step 1: Stop the currently running container
```console
docker stop sonarqube
```
Or using Docker Compose:
```console
docker-compose stop sonarqube
```
#### Step 2: Run the backup command
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
```console
docker run --rm -v /path/to/sonarqube-backups:/backups --volumes-from sonarqube busybox \
cp -a /bitnami/sonarqube /backups/latest
```
### Restoring a backup
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the PostgreSQL database container:
```diff
$ docker run -d --name postgresql \
...
- --volume /path/to/postgresql-persistence:/bitnami/postgresql \
+ --volume /path/to/postgresql-backups/latest:/bitnami/postgresql \
bitnami/postgresql:latest
```
For the SonarQube&trade; container:
```diff
$ docker run -d --name sonarqube \
...
- --volume /path/to/sonarqube-persistence:/bitnami/sonarqube \
+ --volume /path/to/sonarqube-backups/latest:/bitnami/sonarqube \
bitnami/sonarqube:latest
```
The Bitnami SonarQube&trade; Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Notable Changes
@ -213,7 +156,7 @@ For the SonarQube&trade; container:
- The size of the container image has been decreased.
- The configuration logic is now based on Bash scripts in the *rootfs/* folder.
- The SonarQube&trade; container image has been migrated to a "non-root" user approach. Previously the container ran as the `root` user and the SonarQube&trade; daemon was started as the `sonarqube` user. From now on, both the container and the SonarQube&trade; daemon run as user `1001`. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile, or `user: root` in `docker-compose.yml`. Consequences:
- Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating the SonarQube&trade; site by exporting its content, and importing it on a new SonarQube&trade; container. Follow the steps in [Backing up your container](#backing-up-your-container) and [Restoring a backup](#restoring-a-backup) to migrate the data between the old and new container.
- Backwards compatibility is not guaranteed when data is persisted using docker or docker-compose. We highly recommend migrating the SonarQube&trade; site by exporting its content, and importing it on a new SonarQube&trade; container. Before recreating the container, back up or copy the persisted application and database data so you can attach it to the new deployment.
## License