Self-host qBittorrent with Levelrail
A free, self-hosted BitTorrent client with a full web UI for remote download management.
- Authorqbittorrent
- LicenceGPL-2.0-or-later
- Memory256 MiB
- Archarm64
- Services1
How to self-host qBittorrent
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/qbittorrent:5.0.3
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on ports 8080, 6881.
-
Fill in the secrets
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.
qBittorrent requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080, 6881
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-2.0-or-later, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes ports 8080, 6881 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 qBittorrent. 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 qBittorrent docs page.
Deploy qBittorrent your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy qBittorrent from the CLI
levelrail-cli templates deploy qbittorrent --name my-qbittorrent Deploy qBittorrent with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/qbittorrent/deploy qBittorrent configuration
qBittorrent services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| qbittorrent | lscr.io/linuxserver/qbittorrent:5.0.3 | 8080, 6881 | qbittorrent_config -> /configqbittorrent_downloads -> /downloads |
qBittorrent environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8080, 6881
- Volumes
- 2 named mounts: qbittorrent_config -> /config, qbittorrent_downloads -> /downloads
qBittorrent FAQ
How much memory does qBittorrent need?
The catalog lists about 256 MiB of memory for qBittorrent.
Does qBittorrent run on arm64?
For qBittorrent, an arm64 image is published; amd64 is image published.
What licence is qBittorrent under?
qBittorrent is licensed under GPL-2.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does qBittorrent need configuration before it starts?
No. The template fills in its own defaults.
Which ports does qBittorrent use?
qBittorrent listens on ports 8080 and 6881 inside the stack.
Where does qBittorrent keep its data?
In named volumes: qbittorrent_config mounted at /config and qbittorrent_downloads mounted at /downloads.
Can I deploy qBittorrent 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 qbittorrent for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/qbittorrent:5.0.3 is what you deploy there.