readystack/mattermost repository overview

⁠Mattermost

readystack/mattermost:v12.0.1-CE-ubuntu24.04-r1

A cosign-signed build of github.com/mattermost/mattermost v12.0.1 (AGPL-3.0; webapp and server templates/i18n/public are Apache-2.0), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:610dea8db89d188f688dc1e159ef687c3c8df79b63cc9100439cd31a826b2ec9 on 2026-10-28.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products.html#mattermost⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:610dea8db89d188f688dc1e159ef687c3c8df79b63cc9100439cd31a826b2ec9; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/mattermost:v12.0.1-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (mattermost).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v12.0.1-CE-ubuntu24.04-r1 — the release on sale at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/mattermost:v12.0.1-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/mattermost:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/mattermost:v12.0.1-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container running the mattermost server in the foreground, serving both the REST API and the compiled web client, against an EXTERNAL PostgreSQL 15 or later database (Mattermost 12 raised the minimum from 14; against an older server it logs Unsupported Postgres version at start and keeps running, which upstream does not support), which must be reachable by name from the container: a postgres container goes on a user-defined Docker network that the mattermost container joins too (on the default bridge network a container name such as your-db does not resolve and the server exits). This is Team Edition — the free, open-source edition — built from source with all Enterprise code removed rather than merely disabled.

Secrets go in an env file that only you can read, not on the command line, and passwords that only set up the first start come out of it after setup. Create mattermost.env with install -m 600 /dev/null mattermost.env, then write these lines into it with an editor, with your own values (a value typed into a shell stays in its history). Docker reads each line as written: no quotes around a value, no spaces around =.

# The PostgreSQL data source, password included; read at every start. Percent-encode the password's special characters (it is part of a URL).
MM_SQLSETTINGS_DATASOURCE=postgres://mmuser:PASSWORD@your-db:5432/mattermost?sslmode=disable

docker run -d --name mattermost -p 8065:8065 --env-file ./mattermost.env -v mm-data:/mattermost/data -v mm-config:/mattermost/config readystack/mattermost:v12.0.1-CE-ubuntu24.04-r1

mattermost.env holds the database data source, which the server reads at every start; write it without quotes (docker reads the line literally).

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• v12.0.1-CE-ubuntu24.04-r1 — the Mattermost Source Available tree server/enterprise/ (not AGPL) is removed and replaced by an empty package enterprise stub; mmctl's compliance export command (server/cmd/mmctl/commands/compliance_export.go, which imports that tree) and two tests that import it are deleted; server/go.mod builds against the in-tree server/public module; full diff at https://readystack.dev/source/mattermost/v12.0.1/mattermost-v12.0.1-readystack.patch⁠
• v12.0.0-CE-ubuntu24.04-r1 — the Mattermost Source Available tree server/enterprise/ (not AGPL) is removed and replaced by an empty package enterprise stub; mmctl's compliance export command (server/cmd/mmctl/commands/compliance_export.go, which imports that tree) and two tests that import it are deleted; server/go.mod builds against the in-tree server/public module; full diff at https://readystack.dev/source/mattermost/v12.0.0/mattermost-v12.0.0-readystack.patch⁠
• v11.11.1-CE-ubuntu24.04-r1 — the Mattermost Source Available tree server/enterprise/ (not AGPL) removed and replaced by an empty package enterprise stub; mmctl's compliance export command (server/cmd/mmctl/commands/compliance_export.go, which imports that tree) and two tests that import it deleted; server/go.mod built against the in-tree server/public module; full diff at https://readystack.dev/source/mattermost/v11.11.1/mattermost-v11.11.1-readystack.patch⁠ (published 2026-10-20, after this release; notice: https://readystack.dev/source/mattermost/v11.11.1/README.txt⁠)

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is at readystack.dev/buy.html⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:faf91c14c282d1d073b724193f997144c4f03824016c5a6b3766a212ad1b1a8d on 2026-10-27.

— ReadyStack · readystack.dev