Self-host Eclipse Mosquitto with Levelrail
VerifiedA lightweight MQTT broker for connecting IoT devices, sensors, and home automation hubs.
- Authoreclipse-mosquitto
- LicenceEPL-2.0 OR BSD-3-Clause
- Memory128 MiB
- Archarm64
- Services1
How to self-host Eclipse Mosquitto
-
Pull the images
One image is pulled on your server.
Show images
eclipse-mosquitto:2.0.20
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 1883.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 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.
Eclipse Mosquitto requirements
- Memory
- About 128 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 1883
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- EPL-2.0 OR BSD-3-Clause, copyleft license
- Verified. Verified on arm64 with image tag 2.0.20. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 1883 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 Eclipse Mosquitto. 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 Eclipse Mosquitto docs page.
Deploy Eclipse Mosquitto your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Eclipse Mosquitto from the CLI
levelrail-cli templates deploy mosquitto --name my-mosquitto Deploy Eclipse Mosquitto with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/mosquitto/deploy Eclipse Mosquitto configuration
Eclipse Mosquitto services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mosquitto | eclipse-mosquitto:2.0.20 | 1883 | mosquitto_data -> /mosquitto/data |
Eclipse Mosquitto environment variables
| Variable | Service | Value |
|---|---|---|
| MQTT_PASSWORD | mosquitto | Generated at deploy |
| MQTT_USER | mosquitto | Generated at deploy |
Ports and volumes
- Ports
- 1883
- Volumes
- 1 named mount: mosquitto_data -> /mosquitto/data
Eclipse Mosquitto FAQ
How much memory does Eclipse Mosquitto need?
The catalog lists about 128 MiB of memory for Eclipse Mosquitto.
Does Eclipse Mosquitto run on arm64?
For Eclipse Mosquitto, arm64 is tested; amd64 is image published.
What licence is Eclipse Mosquitto under?
Eclipse Mosquitto is licensed under EPL-2.0 OR BSD-3-Clause, which is copyleft, so changes you distribute must be shared under the same terms.
Does Eclipse Mosquitto need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Eclipse Mosquitto use?
Eclipse Mosquitto listens on port 1883 inside the stack.
Where does Eclipse Mosquitto keep its data?
In a named volume: mosquitto_data mounted at /mosquitto/data.
Can I deploy Eclipse Mosquitto 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 mosquitto for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image eclipse-mosquitto:2.0.20 is what you deploy there.