Docker image

Tuleap Community Edition

What for ?

The Tuleap Community Edition docker image allows you to test Tuleap quickly by skipping the installation and customization part. It gives you a fully working Tuleap in minutes with everything preconfigured with sensible defaults.

That’s the recommended way to install Tuleap, especially if you “just want to give it a try”.


You need docker on your host. You might want docker-compose as well.

We are going to pull the official Tuleap Community Edition image. It’s built out of Tuleap official pipelines in rolling release mode.

The following sections assume that you are going to run the Tuleap container as the only “visible” container on the server. That means that Tuleap web container will publish it’s ports (80, 443 and 22) on hosts ports.

Deploy a test environment with docker-compose


The following section is meant for test purpose only. The databases (mysql and redis) are handled by docker and it’s not a recommended setup unless you perfectly understand how to operate (run, backup, restore, troubleshoot) them under docker constraints.

In a directory named tuleap-community-edition (be careful, with docker-compose, directory name matters) create a .env file that defines two variables:
MYSQL_ROOT_PASSWORD=some random strong password
  • TULEAP_FQDN is the full name of the machine you are going to run Tuleap on. As we saw in pre-requisite section, it should be the name of your docker host either from DNS or at very least defined in /etc/hosts (will resolve only locally).

  • MYSQL_ROOT_PASSWORD will be the root password of your mysql instance. We recommend at least 20 chars but only alphabetical & numbers.

Then create a docker-compose.yml file with following content:

version: "2"

    image: tuleap/tuleap-community-edition
    hostname: ${TULEAP_FQDN}
    restart: always
      - "80:80"
      - "443:443"
      - "22:22"
      - tuleap-data:/data
      - db
      - redis
      - mailhog
      - DB_HOST=db
      - DB_ADMIN_USER=root
      - TULEAP_EMAIL_RELAYHOST=mailhog:1025

  # This is for test purpose only. It's not advised to run a production database as a docker container
    image: mysql:5.7
    command: ["--character-set-server=utf8mb4", "--collation-server=utf8mb4_unicode_ci", "--sql-mode=NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"]
      - db57-data:/var/lib/mysql

  # This is for test purpose only. It's not advised to run a production database as a docker container
    image: redis:6
      - redis-data:/data
    command: redis-server --appendonly yes

  # This is for test purpose only. Mailhog is there to capture email traffic
    image: mailhog/mailhog


Run with docker-compose

Go inside the directory where you created the two files and run

$ docker-compose up -d

Then you can follow the progress of the installation with

$ docker-compose logs -f web

Until you see something like:

web_1      | ***********************************************************************************************************
web_1      | * You can get `admin` password with following command: `docker-compose exec web cat /root/.tuleap_passwd` *
web_1      | * Your Tuleap fully qualified domain name is and it's IP address is         *
web_1      | ***********************************************************************************************************
web_1      | Setup Supervisord
web_1      | Let the place for Supervisord
web_1      | 2021-06-15 14:46:50,731 INFO Included extra file "/etc/supervisord.d/backend_workers.ini" during parsing
web_1      | 2021-06-15 14:46:50,731 INFO Included extra file "/etc/supervisord.d/crond.ini" during parsing
web_1      | 2021-06-15 14:46:50,731 INFO Included extra file "/etc/supervisord.d/fpm.ini" during parsing
web_1      | 2021-06-15 14:46:50,731 INFO Included extra file "/etc/supervisord.d/httpd.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Included extra file "/etc/supervisord.d/nginx.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Included extra file "/etc/supervisord.d/postfix.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Included extra file "/etc/supervisord.d/sshd.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Included extra file "/etc/supervisord.d/supervisord-server-credentials.ini" during parsing
web_1      | 2021-06-15 14:46:50,732 INFO Set uid to user 0 succeeded
web_1      | 2021-06-15 14:46:50,769 INFO RPC interface 'supervisor' initialized

You can then quit the logs command (Ctrl+C) and open your browser at the address set in TULEAP_FQDN and that’s it.

During the installation the admin account got a password generated, you can get it by running:

$ docker-compose exec web cat /root/.tuleap_passwd
Site admin password (admin): ...
MySQL application user (tuleapadm): ...

The docker-compose file provided here is for general guidance and you should adapt to your environment. One of the main thing you will want to configure is a proper email relay. By default, we spawned a mailhog image that will catch all mails sent by Tuleap and display to anyone who have access to the interface.

To see the mails captured by mailhog, you should run:

$ docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $(docker-compose ps -q mailhog)

This will gives you the IP address of the container that runs mailhog, you can then open a browser at this IP address on port 8025:

$ xdg-open

Run without docker compose

For anything but tests you should have a dedicated MySQL (version 5.7) and Redis (last stable recommended) databases.

Then you can init docker image in command line:

$ docker run -ti \
    --restart always \
    --publish 22:22 \
    --publish 80:80 \
    --publish 443:443 \
    --hostname \
    -e \
    -e \
    -e DB_ADMIN_USER=root \
    -e TULEAP_REDIS_SERVER=redis \
    -e \
    -v /srv/path/to/data:/data

For future runs you don’t need to pass all the environments:

$ docker run -d \
    --restart always \
    --publish 22:22 \
    --publish 80:80 \
    --publish 443:443 \
    --hostname \
    -e TULEAP_REDIS_SERVER=redis \
    -e \
    -v /srv/path/to/data:/data

Tuleap Enterprise Edition


This image is only available to Tuleap Enterprise subscribers. Please contact your support team to get your access to the private registry.

What for ?

The Tuleap Enterprise Edition docker image is meant to be used in production with an orchestrator (Kubernetes, Swarm, Nomad, etc) or not.

The current image bundles everything in one image to ease the deployment. It’s not recommended to configure your deployment to scale the images (replicate) as it’s not designed to run concurrently.

External Dependencies

The image has two dependencies:

  • A working database with admin credentials (at first run only)

  • A persistent filesystem for data storage

How to

You first need to authenticate toward Tuleap registry:

$ docker login

At first run you will need to provide some information about the platform you want to deploy:

  • The Tuleap server name (without https) as TULEAP_FQDN environment variable

  • The Database server name as DB_HOST environment variable. See database installation for specific configuration.

  • The database admin user (root or equivalent) as DB_ADMIN_USER environment variable

  • The database admin user password as DB_ADMIN_PASSWORD environment variable

You can also modify the behaviour of Tuleap with the following environment variables:

  • TULEAP_DB_SSL_MODE: by default, the connection to the database is not encrypted. You can change that to either:

    • no-verify: connection is encrypted but host certificate is not checked. Your traffic cannot be passively inspected but you are vulnerable to Man In The Middle attacks.

    • verify-ca: connection is encrypted and host certificate is verified. Your db server must use a public trusted certificate. WARNING: perl & python code (used for subversion) cannot enforce this, those parts will do encryption without certificate verification.

  • TULEAP_DB_AZURE_SUFFIX: only needed if you deploy on Microsoft Azure MySQL. It should correspond to first part of DB_HOST (see official documentation)

  • TULEAP_FPM_SESSION_MODE: you can set it to redis so php sessions will be stored in a Redis K/V store. This also activate usage of redis for Tuleap (background events, etc).

  • TULEAP_REDIS_SERVER: needed if you set redis for TULEAP_FPM_SESSION_MODE

  • TULEAP_REDIS_PORT: needed if redis is listening on port that is not 6379 (the default)

  • TULEAP_REDIS_PASSWORD: needed if redis requires a password

  • TULEAP_REDIS_USE_TLS: set to 1 if you want to encrypt the connection to Redis

  • TULEAP_EMAIL_RELAYHOST: email relay host (none by default)

  • TULEAP_EMAIL_ADMIN: email address where all the system emails will be redirected

    • WARNING: You cannot enforce encryption of Redis communication if you enabled Subversion because the underlying code, written in perl, doesn’t support encryption.

The data volume must be mounted on /data inside the container.

You must specify the Tuleap tag you want to run (there is no :latest to avoid mistakes). Please note that you can either:

  • Use the exact Tuleap Enterprise Edition tag like 11.13-4

  • Or just run the head tag of the release like 11.13

$ docker run -ti \
    -e \
    -e \
    -e DB_ADMIN_USER="root" \
    -e DB_ADMIN_PASSWORD="a fine password" \
    -v tuleap-data:/data

The next runs won’t need the environment variable so you can restart with:

$ docker run -d \
    -v tuleap-data:/data


In the context of an orchestrator you don’t need to separate the 2 modes (first run or restart), you can expose the variables in all runs. Please note however that changing the variables in your deployment (compose, helm, etc) won’t have any impact on the container. You will have to manually edit the configuration files to update the relevant data.

When running, the container exposes the following ports:

  • 80 TCP http traffic, automatically redirected to 443

  • 443 TCP https traffic

  • 22 TCP ssh traffic (for git)


Tuleap container generate a self signed certificate can only communicate in https. In order to have a valid certificate for your end users you either need to:

  • Delegate the certificate management to your ingress controller (Kubernetes)

  • Have a reverse proxy in front of the Tuleap container to deal with the certificate

  • I you don’t want to bother with a reverse proxy, you can modify the certificate generated by tuleap and set yours:

    • They key must be /data/etc/pki/tls/private/localhost.key.pem

    • The cert must be /data/etc/pki/tls/certs/localhost.cert.pem

    • If you need something more complex, use a reverse proxy.

Next steps

Once you have a fully running Tuleap you can start using it: issue tracking, source code management, agile planning and more.

Checkout our tutorials and videos on Getting started page.