Request: Provide a multiarch Docker image with arm64 support
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- build-system, devops
Research direction
Locate the existing CI workflow that builds and publishes the official Docker image, then read how its current architecture is selected. Use Docker Buildx or the existing workflow tooling as the starting point; done means the published image supports both amd64 and arm64 without manual rebuilding.
Written by the indexing model from the issue text.
Description
The official Docker image currently supports only the amd64 architecture.
Many users today deploy Rocket.Chat on arm64-based environments such as:
- Raspberry Pi devices
- NAS systems (Synology, TrueNAS, etc.)
- Home servers
- Cloud or VPS providers offering ARM instances
Adding multi-architecture support (amd64 and arm64) would offer several benefits:
- 🧩 Wider compatibility: Rocket.Chat could run on a broader range of hardware without manual rebuilds.
- 🔄 Simplified maintenance: Users could update directly from Docker Hub without building custom images.
- 🔐 Consistent security: Ensures all platforms receive the same updates and patches simultaneously.
- ⚙️ Improved CI/CD workflows: Easier integration into modern multiarch pipelines and container environments.
- 🌱 Energy efficiency: Enables deployments on low-power, cost-effective ARM devices used by small teams and hobbyists.
Multiarch builds can be implemented easily using Docker Buildx or similar tools in the existing CI workflow.
This enhancement would make Rocket.Chat more accessible and reliable across all platforms.
Thank you for considering this improvement and for maintaining such a great open source project.
- Dominant language
- Dockerfile
- Stars
- 336
- Forks
- 226
- Avg merge
- 21d 4h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/Docker.Official.Image
-
Difficulty 4/5 1-2 days Newbie friendliness 25/100
RocketChat/Docker.Official.Image#302 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
RocketChat/Docker.Official.Image#290 · 1 comment · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
RocketChat/Docker.Official.Image#248 · 7 comments · 6 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Docker not installOpen
Difficulty 4/5 3-5 days Newbie friendliness 10/100
RocketChat/Docker.Official.Image#226 · 1 reaction ·
All issues in RocketChat/Docker.Official.Image
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rcpch/digital-growth-charts-react-component-library#304 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 80/100
storytold/craft-libs#1674 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AykutSarac/jsoncrack.com#616 ·