Skip to content
Bitnami Docker Image for Redmine
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add Issues/PRs autoclose Mar 28, 2019
4 4.0.4-ol-7-r34 release Jul 19, 2019
LICENSE Update LICENSE Jun 21, 2018 4.0.4-ol-7-r34 release Jul 19, 2019
docker-compose-postgresql.yml 4.0.3-debian-9-r24 release May 21, 2019
docker-compose.yml 4.0.3-debian-9-r24 release May 21, 2019

What is Redmine?

Redmine is a flexible project management web application. Written using the Ruby on Rails framework, it is cross-platform and cross-database.


Docker Compose

$ curl -sSL > docker-compose.yml
$ docker-compose up -d

Why use Bitnami Images?

  • Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
  • With Bitnami images the latest bug fixes and features are available as soon as possible.
  • Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
  • All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
  • All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
  • Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

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.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Supported tags and respective Dockerfile links

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

Subscribe to project updates by watching the bitnami/redmine GitHub repo.


To run this application you need Docker Engine 1.10.0. Docker Compose is recomended with a version 1.6.0 or later.

How to use this image

Run Redmine with a Database Container

Running Redmine with a database server is the recommended way. You can either use docker-compose or run the containers manually.

Run the application using Docker Compose

The main folder of this repository contains a functional docker-compose.yml file. Run the application using it as shown below:

$ curl -sSL > docker-compose.yml
$ docker-compose up -d

Run the application manually

If you want to run the application manually instead of using docker-compose, these are the basic steps you need to run:

  1. Create a new network for the application and the database:
$ docker network create redmine_network
  1. Start a MariaDB database in the network generated:
$ docker run -d --name mariadb --net=redmine_network \

Note: You need to give the container a name in order to Redmine to resolve the host

  1. Run the Redmine container:
$ docker run -d --name redmine --net=redmine_network -p 80:3000 \

Then you can access your application at http://your-ip/

Run the application using PostgreSQL database

The Bitnami Redmine Docker Image supports both MariaDB and PostgreSQL databases. In order to use a PostgreSQL database you can run the following command:

$ docker-compose -f docker-compose-postgresql.yml up

or use the next docker-compose template:

version: '2'

    image: 'bitnami/postgresql:latest'
      - 'postgresql_data:/bitnami/postgresql'
    image: 'bitnami/redmine:latest'
      - '80:3000'
      - REDMINE_DB_POSTGRES=postgresql
      - 'redmine_data:/bitnami'
      - postgresql
    driver: local
    driver: local

Persisting your application

If you remove the container all your data and configurations 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.

For persistence you should mount a volume at the /bitnami path. Additionally you should mount a volume for persistence of the MariaDB data.

The above examples define docker volumes namely mariadb_data and redmine_data. The Redmine application state will persist as long as these volumes are not removed.

To avoid inadvertent removal of these volumes you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.

Mount host directories as data volumes with Docker Compose

The following docker-compose.yml template demonstrates the use of host directories as data volumes.

      - '/path/to/mariadb-persistence:/bitnami'
      - '/path/to/redmine-persistence:/bitnami'

Mount host directories as data volumes using the Docker command line

  1. Create a network (if it does not exist):
$ docker network create redmine-tier
  1. Create a MariaDB container with host volume:
$ docker run -d --name mariadb --net redmine-tier \
  --volume /path/to/mariadb-persistence:/bitnami \

Note: You need to give the container a name in order to Redmine to resolve the host

  1. Run the Redmine container:
$ docker run -d --name redmine -p 80:3000 --net redmine-tier \
  --volume /path/to/redmine-persistence:/bitnami \

Upgrade this application

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

  1. Get the updated images:
$ docker pull bitnami/redmine:latest
  1. Stop your container
  • For docker-compose: $ docker-compose stop redmine
  • For manual execution: $ docker stop redmine
  1. Take a snapshot of the application state
$ rsync -a /path/to/redmine-persistence /path/to/redmine-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)

Additionally, snapshot the MariaDB data

You can use these snapshots to restore the application state should the upgrade fail.

  1. Remove the currently running container
  • For docker-compose: $ docker-compose rm redmine
  • For manual execution: $ docker rm redmine
  1. Run the new image
  • For docker-compose: $ docker-compose up redmine
  • For manual execution (mount the directories if needed): docker run --name redmine bitnami/redmine:latest


Environment variables

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 file present in this repository:
    - REDMINE_PASSWORD=my_password
  • For manual execution add a -e option with each variable and value:
 $ docker run -d --name redmine --network=redmine_network -p 80:3000 \
     -e REDMINE_PASSWORD=my_password \
     -v /your/local/path/bitnami/redmine:/bitnami \

Available variables:

  • REDMINE_USERNAME: Redmine application username. Default: user
  • REDMINE_PASSWORD: Redmine application password. Default: bitnami1
  • REDMINE_EMAIL: Redmine application email. Default:
  • REDMINE_LANGUAGE: Redmine application default language. Default: en
  • REDMINE_DB_USERNAME: Root user for the application database. Default: root
  • REDMINE_DB_PASSWORD: Root password for the database.
  • REDMINE_DB_MYSQL: Hostname for MySQL server. Default: mariadb
  • REDMINE_DB_POSTGRES: Hostname for PostgreSQL server. No defaults
  • REDMINE_DB_PORT_NUMBER: Port used by database server. Default: 3306

SMTP Configuration

To configure Redmine to send email using SMTP you can set the following environment variables:

  • SMTP_HOST: SMTP host.
  • SMTP_PORT: SMTP port.
  • SMTP_USER: SMTP account user.
  • SMTP_PASSWORD: SMTP account password.
  • SMTP_TLS: Use TLS encription with SMTP. Default true

This would be an example of SMTP configuration using a GMail account:

      - SMTP_PORT=587
      - SMTP_PASSWORD=your_password
  • For manual execution:
 $ docker run -d -p 80:3000 --name redmine --network=redmine_network \
    -e \
    -e SMTP_PORT=587 \
    -e \
    -e SMTP_PASSWORD=your_password \
    -v /your/local/path/bitnami/redmine:/bitnami \


We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.


If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

  • Host OS and version
  • Docker version (docker version)
  • Output of docker info
  • Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
  • The command you used to run the container, and any relevant output you saw (masking any sensitive information)


Copyright (c) 2015-2019 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

You can’t perform that action at this time.