ARM64 support for Mattermost Server

Applies to: Mattermost Server (Team Edition and Enterprise Edition), all versions; all deployment methods (Docker, Kubernetes, Linux packages).

Status: Not officially supported for production, no roadmap commitment (as of 2026-09-01)

Symptoms: Mattermost publishes some arm64 builds, but none are supported for production use; only amd64 is officially supported.

🛑 Problem

Several parts of Mattermost already run on arm64 (like rtcd, mmctl, the desktop app, most plugins), but only amd64 is officially supported for production, due to known plugin incompatibilities and other unresolved issues on arm64. The arm64 server builds that do exist are intended for local development and testing on arm64 platforms, such as macOS, not for production deployment. Docker and Kubernetes images (mattermost/mattermost-team-edition, mattermost/mattermost-enterprise-edition, mattermost/mattermost-enterprise-fips-edition) publish amd64 manifests only, so there is no arm64 container image at all, and FIPS-compliant builds are amd64-only.

Symptoms

• Docker and Kubernetes images have no arm64 manifest; docker manifest inspect returns a single linux/amd64 entry for the team, enterprise, and FIPS editions.
• Linux tarball, RHEL, and Ubuntu server downloads do publish arm64 builds, which can look like full arm64 support when they're intended for local development and testing, not production.
• Third-party projects claiming to build an arm64 Mattermost Enterprise image (for example, community GitHub forks) are not affiliated with or supported by Mattermost.

💡 Recommendation

Deploy Mattermost Server on amd64 hosts for production, regardless of deployment method (Docker, Kubernetes, or Linux package). There is no officially supported arm64 path for production, and general arm64 support isn't on the current roadmap; improvements happen periodically but without a committed timeline.

Existing arm64 builds are for testing only

The arm64 tarball, RHEL, and Ubuntu server downloads, along with mmctl and the desktop app, are intended for local development and testing (for example, running Mattermost natively on an Apple Silicon Mac), not for a production migration.

⚠️ Important: FIPS compliance has no arm64 path in any deployment form. If FIPS is a requirement, the host must stay on amd64.

Additional Resources

Migrate to FIPS-compliant images