linuxserver/docker-qbittorrent
None observed · 2026-08-28
Health v2 · maintenance only
95/100
- Activity 99
- Release rhythm 87
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 6.0
- age_days: 3393
- days_rel: 10
- days_push: 10
- n_releases_24m: 125
Adoption not part of the score
1717 stars · 203 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A Docker container image packaging the qBittorrent BitTorrent client, maintained by LinuxServer.io. It provides regularly updated builds with PUID/PGID user mapping and a s6-overlay base for easy self-hosted deployment.
Use cases
- self-host a qbittorrent server in docker
- run a torrent client with a web ui on my home server
- deploy qbittorrent behind a reverse proxy
- containerized torrent downloading with user permission mapping
- set up qbittorrent on unraid or a NAS
When to choose
- you want a maintained, regularly updated qBittorrent container
- you need easy PUID/PGID mapping for media server setups
- you run a self-hosted stack (e.g., *arr apps) and want a matching torrent client image
When to avoid
- you want to run qBittorrent natively without Docker
- you need a different torrent client like Transmission or Deluge
- you cannot use container runtimes on your host
Facets
application · maturity active
self-hosted container-runtime deployment self-hosted files privacy self-hosted qbittorrent torrent-client docker-image linuxserver webui docker linux
1 source
- readme: https://github.com/linuxserver/docker-qbittorrent · fetched 2026-08-28 · de9b842fbbe1
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| linuxserver/docker-qbittorrent | main | 95 |
For agents
markdown · JSON · MCP: product_card(name="linuxserver/docker-qbittorrent")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem