The LinuxServer.io team brings you another container release featuring:
Find us at: * Blog - all the things you can do with our containers including How-To guides, opinions and much more! * Discord - realtime support / chat with the community and the team. * Discourse - post on our community forum. * Fleet - an online web interface which displays all of our maintained images. * GitHub - view the source for all of our repositories. * Open Collective - please consider helping us by either donating or contributing to our budget
The Qbittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
Our images support multiple architectures such as
x86-64,
arm64and
armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling
ghcr.io/linuxserver/qbittorrentshould retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag | | :----: | --- | | x86-64 | amd64-latest | | arm64 | arm64v8-latest | | armhf | arm32v7-latest |
This image provides various versions that are available via tags.
latesttag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
| Tag | Description | | :----: | --- | | latest | Stable qbittorrent releases | | unstable | Unstable qbittorrent releases |
Here are some example snippets to help you get started creating a container.
Compatible with docker-compose v2 schemas.
--- version: "2.1" services: qbittorrent: image: ghcr.io/linuxserver/qbittorrent container_name: qbittorrent environment: - PUID=1000 - PGID=1000 - TZ=Europe/London - WEBUI_PORT=8080 volumes: - /path/to/appdata/config:/config - /path/to/downloads:/downloads ports: - 6881:6881 - 6881:6881/udp - 8080:8080 restart: unless-stopped
docker run -d \ --name=qbittorrent \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/London \ -e WEBUI_PORT=8080 \ -p 6881:6881 \ -p 6881:6881/udp \ -p 8080:8080 \ -v /path/to/appdata/config:/config \ -v /path/to/downloads:/downloads \ --restart unless-stopped \ ghcr.io/linuxserver/qbittorrent
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate
:respectively. For example,
-p 8080:80would expose port
80from inside the container to be accessible from the host's IP on port
8080outside the container.
| Parameter | Function | | :----: | --- | |
-p 6881| tcp connection port | |
-p 6881/udp| udp connection port | |
-p 8080| http gui | |
-e PUID=1000| for UserID - see below for explanation | |
-e PGID=1000| for GroupID - see below for explanation | |
-e TZ=Europe/London| Specify a timezone to use EG Europe/London | |
-e WEBUI_PORT=8080| for changing the port of the webui, see below for explanation | |
-v /config| Contains all relevant configuration files. | |
-v /downloads| Location of downloads on disk. |
You can set any environment variable from a file by using a special prepend
FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpassword
Will set the environment variable
PASSWORDbased on the contents of the
/run/secrets/mysecretpasswordfile.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional
-e UMASK=022setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (
-vflags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user
PUIDand group
PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance
PUID=1000and
PGID=1000, to find yours use
id useras below:
$ id username uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
The webui is at
:8080and the default username/password is
admin/adminadmin.
Change username/password via the webui in the webui section of settings.
Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port.
For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090
This should alleviate the "white screen" issue.
If you have no webui , check the file /config/qBittorrent/qBittorrent.conf
edit or add the following lines
WebUI\Address=*WebUI\ServerDomains=*
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
docker exec -it qbittorrent /bin/bash
docker logs -f qbittorrent
docker inspect -f '{{ index .Config.Labels "build_version" }}' qbittorrent
docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/qbittorrent
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
docker-compose pull
docker-compose pull qbittorrent
docker-compose up -d
docker-compose up -d qbittorrent
docker image prune
docker pull ghcr.io/linuxserver/qbittorrent
docker stop qbittorrent
docker rm qbittorrent
/configfolder and settings will be preserved)
docker image prune
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once qbittorrent
docker image prune
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-qbittorrent.git cd docker-qbittorrent docker build \ --no-cache \ --pull \ -t ghcr.io/linuxserver/qbittorrent:latest .
The ARM variants can be built on x86_64 hardware using
multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --reset
Once registered you can define the dockerfile to use with
-f Dockerfile.aarch64.
UMASK_SETin favor of UMASK in baseimage, see above for more information.