Self-host Rocket.Chat with Levelrail
VerifiedA full-featured, self-hosted team chat platform with video calls and app integrations.
- Memory1 GiB
- Archarm64
- Services2
How to self-host Rocket.Chat
-
Pull the images
2 images are pulled on your server.
Show images
mongo:7rocketchat/rocket.chat:8.0.1
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Rocket.Chat requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Verified. Verified on arm64 with image tag 7. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 3000 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 Rocket.Chat. 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 Rocket.Chat docs page.
Deploy Rocket.Chat your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Rocket.Chat from the CLI
levelrail-cli templates deploy rocketchat --name my-rocketchat Deploy Rocket.Chat with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/rocketchat/deploy Rocket.Chat configuration
Rocket.Chat services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mongo | mongo:7 | none | rocketchat_mongo_data -> /data/db |
| rocketchat | rocketchat/rocket.chat:8.0.1 | 3000 | none |
Rocket.Chat environment variables
| Variable | Service | Value |
|---|---|---|
| MONGO_OPLOG_URL | rocketchat | Preset by the template |
| MONGO_URL | rocketchat | Preset by the template |
| ROOT_URL | rocketchat | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: rocketchat_mongo_data -> /data/db
Rocket.Chat FAQ
How much memory does Rocket.Chat need?
The catalog lists about 1 GiB of memory for Rocket.Chat across its 2 services.
Does Rocket.Chat run on arm64?
For Rocket.Chat, arm64 is tested; amd64 is image published.
Does Rocket.Chat need configuration before it starts?
No. The template fills in its own defaults.
Which database does Rocket.Chat bundle?
The template includes MongoDB, running as its own service.
Which ports does Rocket.Chat use?
Rocket.Chat listens on port 3000 inside the stack.
Where does Rocket.Chat keep its data?
In a named volume: rocketchat_mongo_data mounted at /data/db.
Can I deploy Rocket.Chat 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 rocketchat for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image mongo:7, rocketchat/rocket.chat:8.0.1 is what you deploy there.