From a979f30d2120d7edf7563f132e9146af3b5a89db Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 5 Mar 2026 10:54:17 +0100 Subject: [PATCH] [bitnami/redmine] Release 6.1.1-debian-12-r13 (#91247) Signed-off-by: Bitnami Bot --- bitnami/redmine/6.1/debian-12/Dockerfile | 9 +++--- bitnami/redmine/README.md | 36 ++++++++++++------------ 2 files changed, 23 insertions(+), 22 deletions(-) diff --git a/bitnami/redmine/6.1/debian-12/Dockerfile b/bitnami/redmine/6.1/debian-12/Dockerfile index e26e441d4e9e..7d441baede50 100644 --- a/bitnami/redmine/6.1/debian-12/Dockerfile +++ b/bitnami/redmine/6.1/debian-12/Dockerfile @@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith" ARG TARGETARCH LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \ - org.opencontainers.image.created="2026-03-02T18:44:03Z" \ + org.opencontainers.image.created="2026-03-05T09:31:06Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/redmine/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/redmine" \ @@ -27,10 +27,11 @@ 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=( \ - "ruby-3.4.8-5-linux-${OS_ARCH}-debian-12" \ + "ruby-3.4.8-6-linux-${OS_ARCH}-debian-12" \ "yq-4.52.4-0-linux-${OS_ARCH}-debian-12" \ "postgresql-client-18.3.0-0-linux-${OS_ARCH}-debian-12" \ "mysql-client-12.2.2-0-linux-${OS_ARCH}-debian-12" \ + "mariadb-lib-12.2.2-0-linux-${OS_ARCH}-debian-12" \ "redmine-6.1.1-5-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ @@ -52,8 +53,8 @@ RUN /opt/bitnami/scripts/mysql-client/postunpack.sh RUN /opt/bitnami/scripts/redmine/postunpack.sh ENV APP_VERSION="6.1.1" \ BITNAMI_APP_NAME="redmine" \ - IMAGE_REVISION="12" \ - LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \ + IMAGE_REVISION="13" \ + LD_LIBRARY_PATH="/opt/bitnami/mariadb/lib:$LD_LIBRARY_PATH" \ PATH="/opt/bitnami/ruby/bin:/opt/bitnami/common/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/mysql/bin:$PATH" EXPOSE 3000 diff --git a/bitnami/redmine/README.md b/bitnami/redmine/README.md index d2be94ace43f..b13e20771c9e 100644 --- a/bitnami/redmine/README.md +++ b/bitnami/redmine/README.md @@ -5,7 +5,7 @@ [Overview of Redmine](https://www.redmine.org/) Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement. -## TL;DR +## TL;DR ```console docker run --name redmine bitnami/redmine:latest @@ -13,7 +13,7 @@ docker run --name redmine bitnami/redmine:latest **Warning**: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Environment Variables](#environment-variables) section for a more secure deployment. -## Why use Bitnami Secure Images? +## 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? @@ -30,15 +30,15 @@ Each image comes with valuable security metadata. You can view the metadata in [ If you are looking for our previous generation of images based on Debian Linux, please see the [Bitnami Legacy registry](https://hub.docker.com/u/bitnamilegacy). -## How to deploy Redmine in Kubernetes? +## How to deploy Redmine in Kubernetes? Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the [Bitnami Redmine Chart GitHub repository](https://github.com/bitnami/charts/tree/master/bitnami/redmine). -## Supported tags and respective `Dockerfile` links +## Supported tags and respective `Dockerfile` links Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html). -## Get this image +## Get this image The recommended way to get the Bitnami Redmine Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/redmine). @@ -60,7 +60,7 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` -## Persisting your application +## 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. @@ -72,11 +72,11 @@ To avoid inadvertent removal of volumes, you can [mount host directories as data > **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. -## Configuration +## Configuration The following section describes the supported environment variables -### Environment variables +### Environment variables The following tables list the main variables you can set. @@ -126,13 +126,13 @@ The following tables list the main variables you can set. When you start the Redmine 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. -### FIPS configuration in Bitnami Secure Images +### FIPS configuration in Bitnami Secure Images The Bitnami Redmine Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: - `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`. -## Logging +## Logging The Bitnami Redmine Docker image sends the container logs to `stdout`. To view the logs: @@ -148,11 +148,11 @@ docker-compose logs redmine 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. -## Customize this image +## Customize this image The Bitnami Redmine Docker image is designed to be extended. -### Extend this image +### Extend this image Before extending this image, please note there are certain configuration settings you can modify using the original image: @@ -163,13 +163,13 @@ If your desired customizations cannot be covered using the methods mentioned abo ```Dockerfile FROM bitnami/redmine -### Put your customizations below +### Put your customizations below ... ``` -## Maintenance +## Maintenance -### Backing up your container +### Backing up your container To backup your data, configuration and logs, follow these simple steps: @@ -194,7 +194,7 @@ docker run --rm -v /path/to/redmine-backups:/backups --volumes-from redmine busy cp -a /bitnami/redmine /backups/latest ``` -### Restoring a backup +### Restoring a backup Restoring a backup is as simple as mounting the backup as volumes in the containers. @@ -218,7 +218,7 @@ For the Redmine container: bitnami/redmine:latest ``` -## Notable Changes +## Notable Changes ### 4.2.1-debian-10-r70 @@ -230,7 +230,7 @@ For the Redmine container: - `REDMINE_DB_POSTGRES` in favor of `REDMINE_DATABASE_HOST`. When used, `REDMINE_DATABASE_TYPE=postgresql` will also be set. - `REDMINE_DB_MYSQL`, in favor of `REDMINE_DATABASE_HOST`. Whenused, `REDMINE_DATABASE_TYPE=mariadb` will also be set. -## License +## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.