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

[bitnami/redmine] Release 6.1.1-debian-12-r8 (#91101)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-02-25 11:29:13 +01:00
committed by GitHub
parent f45c0a4a62
commit 33f8dc341c
2 changed files with 7 additions and 264 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/redmine/6.1/debian-12/Dockerfile
+6 -5
View File
@@ -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-02-18T12:43:04Z" \
org.opencontainers.image.created="2026-02-25T10:12:03Z" \
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" \
@@ -22,16 +22,16 @@ ENV OS_ARCH="${TARGETARCH:-amd64}" \
COPY prebuildfs /
SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
# Install required system packages and dependencies
RUN install_packages acl ca-certificates curl ghostscript git gsfonts imagemagick libaudit1 libbrotli1 libbsd0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libedit2 libffi8 libgcc-s1 libgmp10 libgnutls30 libgssapi-krb5-2 libhogweed6 libicu72 libidn2-0 libjemalloc2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.5-0 liblz4-1 liblzma5 libmariadb3 libmd0 libncurses6 libnettle8 libnghttp2-14 libp11-kit0 libpam0g libpcre2-8-0 libpq5 libpsl5 libreadline-dev librtmp1 libsasl2-2 libssh2-1 libssl-dev libssl3 libstdc++6 libtasn1-6 libtinfo6 libunistring2 libuuid1 libxml2 libxslt1.1 libyaml-0-2 libyaml-dev libzstd1 procps zlib1g
RUN install_packages acl ca-certificates curl ghostscript git gsfonts imagemagick libaudit1 libbrotli1 libbsd0 libcap-ng0 libcom-err2 libcrypt1 libcurl4 libedit2 libffi8 libgcc-s1 libgmp10 libgnutls30 libgssapi-krb5-2 libhogweed6 libicu72 libidn2-0 libjemalloc2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libldap-2.5-0 liblz4-1 liblzma5 libmariadb3 libmd0 libncurses6 libnettle8 libnghttp2-14 libp11-kit0 libpam0g libpcre2-8-0 libpsl5 libreadline-dev librtmp1 libsasl2-2 libssh2-1 libssl-dev libssl3 libstdc++6 libtasn1-6 libtinfo6 libunistring2 libuuid1 libxml2 libxslt1.1 libyaml-0-2 libyaml-dev libzstd1 procps zlib1g
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-3-linux-${OS_ARCH}-debian-12" \
"yq-4.52.4-0-linux-${OS_ARCH}-debian-12" \
"postgresql-client-18.2.0-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" \
"redmine-6.1.1-0-linux-${OS_ARCH}-debian-12" \
"redmine-6.1.1-1-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -52,7 +52,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="7" \
IMAGE_REVISION="8" \
LD_LIBRARY_PATH="/opt/bitnami/postgresql/lib:$LD_LIBRARY_PATH" \
PATH="/opt/bitnami/ruby/bin:/opt/bitnami/common/bin:/opt/bitnami/postgresql/bin:/opt/bitnami/mysql/bin:$PATH"
EXPOSE 3000
bitnami/redmine/README.md
+1 -259
View File
@@ -62,60 +62,6 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM
docker build -t bitnami/APP:latest .
```
## How to use this image
Redmine requires access to a MySQL, MariaDB or PostgreSQL database to store information. We'll use the [Bitnami Docker Image for MariaDB](https://github.com/bitnami/containers/tree/main/bitnami/mariadb) for the database requirements.
### Using the Docker Command Line
#### Step 1: Create a network
```console
docker network create redmine-network
```
#### Step 2: Create a volume for MariaDB persistence and create a MariaDB container
```console
$ docker volume create --name mariadb_data
docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_redmine \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_redmine \
--network redmine-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
```
#### Step 3: Create volumes for Redmine persistence and launch the container
```console
$ docker volume create --name redmine_data
docker run -d --name redmine \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env REDMINE_DATABASE_USER=bn_redmine \
--env REDMINE_DATABASE_PASSWORD=bitnami \
--env REDMINE_DATABASE_NAME=bitnami_redmine \
--network redmine-network \
--volume redmine_data:/bitnami/redmine \
bitnami/redmine: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/redmine/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/redmine).
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,67 +72,8 @@ The above examples define the Docker volumes named `mariadb_data` and `redmine_d
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/redmine/docker-compose.yml) file present in this repository:
```diff
mariadb:
...
volumes:
- - ariadb_data:/bitnami/mariadb
+ - /path/to/mariadb-persistence:/bitnami/mariadb
...
redmine:
...
volumes:
- - redmine_data:/bitnami/redmine
+ - /path/to/redmine-persistence:/bitnami/redmine
...
-volumes:
- mariadb_data:
- driver: local
- redmine_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 redmine-network
```
#### Step 2. Create a MariaDB container with host volume
```console
docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_redmine \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_redmine \
--network redmine-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
```
#### Step 3. Create the Redmine container with host volumes
```console
docker run -d --name redmine \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env REDMINE_DATABASE_USER=bn_redmine \
--env REDMINE_DATABASE_PASSWORD=bitnami \
--env REDMINE_DATABASE_NAME=bitnami_redmine \
--network redmine-network \
--volume /path/to/redmine-persistence:/bitnami/redmine \
bitnami/redmine:latest
```
## Configuration
### Environment variables
@@ -235,101 +122,7 @@ docker run -d --name redmine \
| `REDMINE_DAEMON_GROUP` | Redmine system group. | `redmine` |
| `REDMINE_DEFAULT_DATABASE_HOST` | Default database server host. | `mariadb` |
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. 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/redmine/docker-compose.yml) file present in this repository:
```yaml
redmine:
...
environment:
- REDMINE_PASSWORD=my_password
...
```
- For manual execution add a `--env` option with each variable and value:
```console
$ docker run -d --name redmine -p 80:8080 -p 443:8443 \
--env REDMINE_PASSWORD=my_password \
--network redmine-tier \
--volume /path/to/redmine-persistence:/bitnami \
bitnami/redmine:latest
```
### Examples
#### SMTP configuration using a Gmail account
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/redmine/docker-compose.yml) file present in this repository:
```yaml
redmine:
...
environment:
- REDMINE_DATABASE_USER=bn_redmine
- REDMINE_DATABASE_NAME=bitnami_redmine
- ALLOW_EMPTY_PASSWORD=yes
- REDMINE_SMTP_HOST=smtp.gmail.com
- REDMINE_SMTP_PORT=587
- REDMINE_SMTP_USER=your_email@gmail.com
- REDMINE_SMTP_PASSWORD=your_password
...
```
- For manual execution:
```console
$ docker run -d --name redmine -p 80:8080 -p 443:8443 \
--env REDMINE_DATABASE_USER=bn_redmine \
--env REDMINE_DATABASE_NAME=bitnami_redmine \
--env REDMINE_SMTP_HOST=smtp.gmail.com \
--env REDMINE_SMTP_PORT=587 \
--env REDMINE_SMTP_USER=your_email@gmail.com \
--env REDMINE_SMTP_PASSWORD=your_password \
--network redmine-tier \
--volume /path/to/redmine-persistence:/bitnami \
bitnami/redmine:latest
```
#### Connect Redmine container to an existing database
The Bitnami Redmine container supports connecting the Redmine application to an external database. This would be an example of using an external database for Redmine.
- Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/redmine/docker-compose.yml) file present in this repository:
```diff
redmine:
...
environment:
- - REDMINE_DATABASE_HOST=mariadb
+ - REDMINE_DATABASE_HOST=mariadb_host
- REDMINE_DATABASE_PORT_NUMBER=3306
- REDMINE_DATABASE_NAME=redmine_db
- REDMINE_DATABASE_USER=redmine_user
- - ALLOW_EMPTY_PASSWORD=yes
+ - REDMINE_DATABASE_PASSWORD=redmine_password
...
```
- For manual execution:
```console
$ docker run -d --name redmine\
-p 8080:8080 -p 8443:8443 \
--network redmine-network \
--env REDMINE_DATABASE_HOST=mariadb_host \
--env REDMINE_DATABASE_PORT_NUMBER=3306 \
--env REDMINE_DATABASE_NAME=redmine_db \
--env REDMINE_DATABASE_USER=redmine_user \
--env REDMINE_DATABASE_PASSWORD=redmine_password \
--volume redmine_data:/bitnami/redmine \
bitnami/redmine:latest
```
In case the database already contains data from a previous Redmine installation, you need to set the variable `REDMINE_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 `REDMINE_SKIP_BOOTSTRAP` to `yes`, values for environment variables such as `REDMINE_USERNAME`, `REDMINE_PASSWORD` or `REDMINE_EMAIL` will be ignored.
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
@@ -372,17 +165,6 @@ FROM bitnami/redmine
...
```
Here is an example of extending to install custom plugins:
```Dockerfile
FROM bitnami/redmine
### Install custom plugins
RUN cd /opt/bitnami/redmine && \
git clone https://github.com/user_name/name_of_the_plugin.git plugins/name_of_the_plugin && \
bundle config set frozen false && bundle install && bundle config set frozen true
```
## Maintenance
### Backing up your container
@@ -434,46 +216,6 @@ For the Redmine container:
bitnami/redmine:latest
```
### Upgrade this image
Bitnami provides up-to-date versions of MariaDB and Redmine, 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 Redmine container. For the MariaDB upgrade see: <https://github.com/bitnami/containers/tree/main/bitnami/mariadb#upgrade-this-image>
The `bitnami/redmine: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/redmine:latest`. However it is recommended to use [tagged versions](https://hub.docker.com/r/bitnami/redmine/tags/).
#### Step 1: Get the updated image
```console
docker pull bitnami/redmine:latest
```
#### Step 2: Stop the running container
Stop the currently running container using the command
```console
docker-compose stop redmine
```
#### 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 redmine
```
#### 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
### 4.2.1-debian-10-r70