Self-host Flood with Levelrail
A modern web interface for rTorrent, qBittorrent, Transmission and Deluge.
- Authorjesec
- LicenceGPL-3.0-only
- Memory256 MiB
- Services1
How to self-host Flood
-
Pull the images
One image is pulled on your server.
Show images
jesec/flood:4.16.4
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
1 setting is 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
- Create the admin user on first visit, then point Flood at your torrent client.
Flood requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-only, 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 Flood. 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 Flood docs page.
Deploy Flood your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Flood from the CLI
levelrail-cli templates deploy flood --name my-flood Deploy Flood with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/flood/deploy Flood configuration
Flood services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| flood | jesec/flood:4.16.4 | 3000 | config -> /configdata -> /data |
Flood environment variables
| Variable | Service | Value |
|---|---|---|
| HOME | flood | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: config -> /config, data -> /data
Flood FAQ
How much memory does Flood need?
The catalog lists about 256 MiB of memory for Flood.
Does Flood run on arm64?
For Flood, arm64 support is not confirmed; amd64 is unknown.
What licence is Flood under?
Flood is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does Flood need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Flood use?
Flood listens on port 3000 inside the stack.
Where does Flood keep its data?
In named volumes: config mounted at /config and data mounted at /data.
Can I deploy Flood 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 Flood, 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 jesec/flood:4.16.4 is what you deploy there.