Self-host VerneMQ with Levelrail
A scalable MQTT broker with a status page and a data volume, with one generated admin user and anonymous access off. MQTT on 1883 stays private.
- Authorvernemq
- LicenceApache-2.0
- Memory256 MiB
- Services1
How to self-host VerneMQ
-
Pull the images
One image is pulled on your server.
Show images
vernemq/vernemq:2.2.1-alpine
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 8888, 1883.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 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.
After the first start
- Connect MQTT clients in this project to vernemq:1883 as user admin with the generated password from the app secrets.
VerneMQ requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8888, 1883
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then VerneMQ. 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 VerneMQ docs page.
Deploy VerneMQ your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy VerneMQ from the CLI
levelrail-cli templates deploy vernemq --name my-vernemq Deploy VerneMQ with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/vernemq/deploy VerneMQ configuration
VerneMQ services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| vernemq | vernemq/vernemq:2.2.1-alpine | 8888, 1883 | vernemq_data -> /vernemq/data |
VerneMQ environment variables
| Variable | Service | Value |
|---|---|---|
| DOCKER_VERNEMQ_ACCEPT_EULA | vernemq | Preset by the template |
| DOCKER_VERNEMQ_ALLOW_ANONYMOUS | vernemq | Preset by the template |
| DOCKER_VERNEMQ_USER_admin | vernemq | Generated at deploy |
Ports and volumes
- Ports
- 8888, 1883
- Volumes
- 1 named mount: vernemq_data -> /vernemq/data
VerneMQ FAQ
How much memory does VerneMQ need?
The catalog lists about 256 MiB of memory for VerneMQ.
Does VerneMQ run on arm64?
For VerneMQ, arm64 support is not confirmed; amd64 is unknown.
What licence is VerneMQ under?
VerneMQ is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does VerneMQ need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does VerneMQ use?
VerneMQ listens on ports 8888 and 1883 inside the stack.
Where does VerneMQ keep its data?
In a named volume: vernemq_data mounted at /vernemq/data.
Can I deploy VerneMQ on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for VerneMQ, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image vernemq/vernemq:2.2.1-alpine is what you deploy there.