Self-host Deluge with Levelrail
A lightweight BitTorrent client with a web interface and plugins. GPL-3.0 licensed. The web UI starts with the default password deluge, so change it on first sign in (Preferences, Interface). Only the web UI is published, so incoming peer connections are limited.
- Authordeluge-torrent
- LicenceGPL-3.0-or-later
- Memory256 MiB
- Archarm64
- Services1
How to self-host Deluge
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/deluge:2.2.0
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 8112.
-
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.
Deluge requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8112
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-or-later, 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 Deluge. 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 Deluge docs page.
Deploy Deluge your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Deluge from the CLI
levelrail-cli templates install deluge --name my-deluge Deploy Deluge with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/deluge/install \
-d '{
"name": "my-deluge"
}' Deluge configuration
Deluge services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| deluge | lscr.io/linuxserver/deluge:2.2.0 | 8112 | config -> /configdownloads -> /downloads |
Deluge environment variables
| Variable | Service | Value |
|---|---|---|
| PGID | deluge | Preset by the template |
| PUID | deluge | Preset by the template |
| TZ | deluge | Preset by the template |
Ports and volumes
- Ports
- 8112
- Volumes
- 2 named mounts: config -> /config, downloads -> /downloads
Deluge FAQ
How much memory does Deluge need?
The catalog lists about 256 MiB of memory for Deluge.
Does Deluge run on arm64?
For Deluge, an arm64 image is published; amd64 is image published.
What licence is Deluge under?
Deluge is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does Deluge need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Deluge use?
Deluge listens on port 8112 inside the stack.
Where does Deluge keep its data?
In named volumes: config mounted at /config and downloads mounted at /downloads.
Can I deploy Deluge 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 Deluge, 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 lscr.io/linuxserver/deluge:2.2.0 is what you deploy there.