Self-host Dagu with Levelrail
A workflow engine that runs DAGs defined in plain YAML files, with a web UI.
- Authordagucloud
- LicenceGPL-3.0
- Memory256 MiB
- Services1
How to self-host Dagu
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/dagucloud/dagu:2.25.4
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 4 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.
Dagu requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft 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 Dagu. 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 Dagu docs page.
Deploy Dagu your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Dagu from the CLI
levelrail-cli templates deploy dagu --name my-dagu Deploy Dagu with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/dagu/deploy Dagu configuration
Dagu services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| dagu | ghcr.io/dagucloud/dagu:2.25.4 | 8080 | dagu_data -> /var/lib/dagu |
Dagu environment variables
| Variable | Service | Value |
|---|---|---|
| DAGU_AUTH_BASIC_PASSWORD | dagu | Generated at deploy |
| DAGU_AUTH_BASIC_USERNAME | dagu | Preset by the template |
| DAGU_AUTH_MODE | dagu | Preset by the template |
| DAGU_HOST | dagu | Preset by the template |
| DAGU_PORT | dagu | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: dagu_data -> /var/lib/dagu
Dagu FAQ
How much memory does Dagu need?
The catalog lists about 256 MiB of memory for Dagu.
Does Dagu run on arm64?
For Dagu, arm64 support is not confirmed; amd64 is unknown.
What licence is Dagu under?
Dagu is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Dagu need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Dagu use?
Dagu listens on port 8080 inside the stack.
Where does Dagu keep its data?
In a named volume: dagu_data mounted at /var/lib/dagu.
Can I deploy Dagu 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 dagu for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/dagucloud/dagu:2.25.4 is what you deploy there.