Run qbittorrent rootless and distroless.
qBittorrent is a bittorrent client programmed in C++ / Qt that uses libtorrent (sometimes called libtorrent-rasterbar) by Arvid Norberg.
What can I do with this? This image will run qbittorrent rootless and distroless, for maximum security. Enjoy your adventures on the high sea as safe as it can be.
Why should I run this image and not the other image(s) that already exist? Good question! Because ...
Important
- ... this image runs rootless as 1000:1000
- ... this image has no shell since it is distroless
- ... this image has a health check
- ... this image runs read-only
- ... this image is automatically scanned for CVEs before and after publishing
- ... this image is created via a secure and pinned CI/CD process
- ... this image verifies all external payloads
- ... this image is very small
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
Below you find a comparison between this image and the most used or original one.
image | 11notes/qbittorrent:5.1.2 | linuxserver/qbittorrent:5.1.2 |
---|---|---|
image size on disk | 21.8MB | 204MB |
process UID/GID | 1000/1000 | 0/0 |
distroless? | ✅ | ❌ |
rootless? | ✅ | ❌ |
- /qbittorrent/etc - Directory of your qBittorrent.conf and other files
- /qbittorrent/var - Directory of your SQlite database for qBittorrent
name: "arr"
services:
qbittorrent:
image: "11notes/qbittorrent:5.1.2"
read_only: true
environment:
TZ: "Europe/Zurich"
volumes:
- "qbittorrent.etc:/qbittorrent/etc"
- "qbittorrent.var:/qbittorrent/var"
ports:
- "3000:3000/tcp"
networks:
frontend:
restart: "always"
volumes:
qbittorrent.etc:
qbittorrent.var:
networks:
frontend:
Parameter | Value | Description |
---|---|---|
user |
docker | user name |
uid |
1000 | user identifier |
gid |
1000 | group identifier |
home |
/qbittorrent | home directory of user docker |
login |
admin // qbittorrent | login using default config |
Parameter | Value | Default |
---|---|---|
TZ |
Time Zone | |
DEBUG |
Will activate debug option for container image and app (if available) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is of my opinion that the :latest
tag is dangerous. Many times, I’ve introduced breaking changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest semver, simply use the short versions of semver. Instead of using :5.1.2
you can use :5
or :5.1
. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest
but at least fixed to a major or minor version.
If you still insist on having the bleeding edge release of this app, simply use the :rolling
tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/qbittorrent:5.1.2
docker pull ghcr.io/11notes/qbittorrent:5.1.2
docker pull quay.io/11notes/qbittorrent:5.1.2
Important
This image is not based on another image but uses scratch as the starting layer. The image consists of the following distroless layers that were added:
- 11notes/distroless - contains users, timezones and Root CA certificates
Tip
- Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
- Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services
Caution
- If you use the image with the default configuration, please make sure to change the default web ui login account password or provide your own qBittorrent.conf
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases for breaking changes. If you have any problems with using this image simply raise an issue, thanks. If you have a question or inputs please create a new discussion instead of an issue. You can find all my other repositories on github.
created 03.07.2025, 07:30:38 (CET)