# Self-host qBittorrent

> A free, self-hosted BitTorrent client with a full web UI for remote download management.

- Page: https://levelrail.com/templates/qbittorrent/
- JSON: https://levelrail.com/templates/qbittorrent.json
- Category: Media
- Licence: GPL-2.0-or-later (Copyleft license)
- Source: https://github.com/qbittorrent/qBittorrent
- Upstream docs: https://github.com/qbittorrent/qBittorrent/wiki

## Requirements
- Memory: about 256 MiB
- amd64: published, arm64: published
- Needs configuration before start: no
- Pinned image tag: 5.0.3

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| qbittorrent | lscr.io/linuxserver/qbittorrent | 5.0.3 | 8080, 6881 | qbittorrent_config -> /config; qbittorrent_downloads -> /downloads |

## Deploy

### CLI

```bash
levelrail-cli templates deploy qbittorrent --name my-qbittorrent
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/qbittorrent/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### 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.

Self-host qBittorrent, qBittorrent docker compose file, deploy qBittorrent on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
