Self-host Mattermost with Levelrail

An open-source, self-hosted alternative to Slack for team messaging and collaboration.

  • Memory1 GiB
  • Services2

How to self-host Mattermost

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • mattermost/mattermost-team-edition:release-10
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 8065.

  3. Fill in the secrets

    2 secrets are generated and stored encrypted, 4 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Mattermost requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 not available
Ports
8065
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
not yet recorded
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8065 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Mattermost. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Mattermost docs page.

Deploy Mattermost your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Mattermost from the CLI

levelrail-cli templates deploy mattermost --name my-mattermost

Deploy Mattermost with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/mattermost/deploy

Mattermost configuration

Mattermost services

ServiceImagePortsVolumes
db postgres:16-alpine none mattermost_db_data -> /var/lib/postgresql/data
mattermost mattermost/mattermost-team-edition:release-10 8065 mattermost_data -> /mattermost/data

Mattermost environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
MM_SERVICESETTINGS_SITEURL mattermost Preset by the template
MM_SQLSETTINGS_DATASOURCE mattermost Generated at deploy
MM_SQLSETTINGS_DRIVERNAME mattermost Preset by the template

Ports and volumes

Ports
8065
Volumes
2 named mounts: mattermost_db_data -> /var/lib/postgresql/data, mattermost_data -> /mattermost/data

Mattermost FAQ

How much memory does Mattermost need?

The catalog lists about 1 GiB of memory for Mattermost across its 2 services.

Does Mattermost run on arm64?

For Mattermost, amd64 only, no arm64 image; amd64 is image published.

Does Mattermost need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Mattermost bundle?

The template includes Postgres, running as its own service.

Which ports does Mattermost use?

Mattermost listens on port 8065 inside the stack.

Where does Mattermost keep its data?

In named volumes: mattermost_db_data mounted at /var/lib/postgresql/data and mattermost_data mounted at /mattermost/data.

Can I deploy Mattermost on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id mattermost for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, mattermost/mattermost-team-edition:release-10 is what you deploy there.

levelrail-cli templates deploy mattermost --name my-mattermost