Need help with zammad-docker-compose?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

134 Stars 112 Forks GNU Affero General Public License v3.0 311 Commits 2 Opened issues


Zammad Docker images for docker-compose

Services available


Need anything else?

Contributors list

Welcome to Zammad

Zammad is a web based open source helpdesk/ticket system with many features to manage customer communication via several channels like telephone, facebook, twitter, chat and e-mails. It is distributed under the GNU AFFERO General Public License (AGPL). Do you receive many e-mails and want to answer them with a team of agents? You're going to love Zammad!

Use case for this repo

This repo is meant to be the starting point for somebody who likes to use dockerized multi-container Zammad in production.

Getting started with zammad-docker-compose

CI Status

CI Status

Using a reverse proxy

In environments with more then one web applications it is necessary to use a reverse proxy to route connections to port 80 and 443 to the right application. To run Zammad behind a revers proxy, we provide

as a starting point.
  1. Copy
    to your own configuration, e.g.

    cp ./.examples/proxy/docker-compose.proxy-example.yml ./
  2. Modify the environment variable
    and the name of the external network in
    to fit your environment.
  3. Run docker-composer commands with the default and your configuration, e.g.
    docker-compose -f docker-compose.yml -f up -d


for an example proxy project.

Like this, you can add your
to a branch of your Git repository and stay up to date by merging changes to your branch.

Using Rancher

RANCHER_URL=http://RANCHER_HOST:8080 rancher-compose --env-file=.env up

Running without Elasticsearch

Elasticsearch is an optional, but strongly recommended dependency for Zammad. More details can be found in the documentation. There are however certain scenarios when running without Elasticsearch may be desired, e.g. for very small teams, for teams with limited budget or as a temporary solution for an unplanned Elasticsearch downtime or planned cluster upgrade.

Elasticsearch is enabled by default in the example

file. It is also by default required to run the "zammad-init" command. Disabling Elasticsearch is possible by setting a special environment variable:
for the
container and removing all references to Elasticsearch everywhere else: the
container, it's volume and links to it.


From =< 3.3.0-12

We've updated the Elasticsearch image from 5.6 to 7.6. As there is no direct upgrade path we have to delete all Elasticsearch indices and rebuild them. Do the following to empty the ES docker volume:

docker-compose stop
set -o pipefail DOCKER_VOLUME="$(docker volume inspect zammaddockercompose_elasticsearch-data | grep Mountpoint | sed -e 's#.*": "##g' -e 's#",##')/*"
echo "${DOCKER_VOLUME}" #check this is a valid docker volume path! if not do not proceed or you might lose data!
rm -r $(docker volume inspect zammaddockercompose_elasticsearch-data | grep Mountpoint | sed -e 's#.*": "##g' -e 's#",##')/*
docker-compose start

To workaround the changes in the PostgreSQL 9.6 container do the following:

docker-compose start
docker exec -it zammaddockercompose_zammad-postgresql_1 bash
psql --username postgres --dbname zammad_production

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.