Supported tags and respective
What is Redmine?
Redmine is a free and open source, web-based project management and issue tracking tool. It allows users to manage multiple projects and associated subprojects. It features per project wikis and forums, time tracking, and flexible role based access control. It includes a calendar and Gantt charts to aid visual representation of projects and their deadlines. Redmine integrates with various version control systems and includes a repository browser and diff viewer.
How to use this image
Run Redmine with SQLite3
This is the simplest setup; just run redmine.
docker run -d --name some-redmine redmine
not for multi-user production use (redmine wiki)
Run Redmine with a Database Container
Running Redmine with a database server is the recommened way.
start a database container
docker run -d --name some-postgres -e POSTGRES_PASSWORD=secret -e POSTGRES_USER=redmine postgres
--link some-mysql:mysqlwhen running redmine)
docker run -d --name some-mysql -e MYSQL_ROOT_PASSWORD=secret -e MYSQL_DATABASE=redmine mysql
docker run -d --name some-redmine --link some-postgres:postgres redmine
Alternative Web Server
The other tags in this repository, like those with
passenger, use the same environment and
--links as the default tags that use WEBrick (
rails s) but instead give you the option of a different web and application server.
passenger uses Phusion Passenger.
tini is used for reaping zombies.
Accessing the Application
Currently, the default user and password from upstream is admin/admin (logging into the application).
Where to Store Data
Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the
redmine images to familiarize themselves with the options available, including:
- Let Docker manage the storage of your files by writing the files to disk on the host system using its own internal volume management. This is the default and is easy and fairly transparent to the user. The downside is that the files may be hard to locate for tools and applications that run directly on the host system, i.e. outside containers.
- Create a data directory on the host system (outside the container) and mount this to a directory visible from inside the container. This places the database files in a known location on the host system, and makes it easy for tools and applications on the host system to access the files. The downside is that the user needs to make sure that the directory exists, and that e.g. directory permissions and other security mechanisms on the host system are set up correctly.
The Docker documentation is a good starting point for understanding the different storage options and variations, and there are multiple blogs and forum postings that discuss and give advice in this area. We will simply show the basic procedure here for the latter option above:
- Create a data directory on a suitable volume on your host system, e.g.
redminecontainer like this:
docker run -d --name some-redmine -v /my/own/datadir:/usr/src/redmine/files --link some-postgres:postgres redmine
-v /my/own/datadir:/usr/src/redmine/files part of the command mounts the
/my/own/datadir directory from the underlying host system as
/usr/src/redmine/files inside the container, where Redmine will store uploaded files.
Note that users on host systems with SELinux enabled may see issues with this. The current workaround is to assign the relevant SELinux policy type to the new data directory so that the container will be allowed to access it:
chcon -Rt svirt_sandbox_file_t /my/own/datadir
If you'd like to be able to access the instance from the host without the container's IP, standard port mappings can be used. Just add
-p 3000:3000 to the
docker run arguments and then access either
http://host-ip:3000 in a browser.
When you start the
redmine image, you can adjust the configuration of the instance by passing one or more environment variables on the
docker run command line.
This variable allows you to control if
rake db:migrate is run on container start. Just set the variable to a non-empty string like
true and the migrate script will not automatically run on container start.
db:migrate will also not run if you start your image with something other than the default
bash. See the current
docker-entrypoint.sh in your image for details.
This variable is used to create an initial
config/secrets.yml and set the
secret_key_base value, which is "used by Rails to encode cookies storing session data thus preventing their tampering. Generating a new secret token invalidates all existing sessions after restart" (session store). If you do not set this variable or provide a
secrets.yml one will be generated using
Supported Docker versions
This image is officially supported on Docker version 1.8.0.
Support for older versions (down to 1.0) is provided on a best-effort basis.
Docker, Inc is the company behind the open source Docker platform and the growing Docker ecosystem of contributors, partners and adopters revolutionizing the way distributed applications are built, shipped, and run.
Copyright (c) 2014-2015 Docker, Inc.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.