Need help with docker-qbittorrent?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

linuxserver
158 Stars 49 Forks GNU General Public License v3.0 229 Commits 12 Opened issues

Services available

!
?

Need anything else?

Contributors list

linuxserver.io

Blog Discord Discourse Fleet GitHub Open Collective

The LinuxServer.io team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

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

linuxserver/qbittorrent

GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry MicroBadger Layers Docker Pulls Docker Stars Jenkins Build LSIO CI

The Qbittorrent project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.

qbittorrent

Supported Architectures

Our images support multiple architectures such as

x86-64
,
arm64
and
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/qbittorrent
should 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 |

Version Tags

This image provides various versions that are available via tags.

latest
tag 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 |

Usage

Here are some example snippets to help you get started creating a container.

docker-compose (recommended)

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 cli

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

Parameters

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:80
would expose port
80
from inside the container to be accessible from the host's IP on port
8080
outside 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. |

Environment variables from files (Docker secrets)

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

PASSWORD
based on the contents of the
/run/secrets/mysecretpassword
file.

Umask for running applications

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=022
setting. 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.

User / Group Identifiers

When using volumes (

-v
flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user
PUID
and 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=1000
and
PGID=1000
, to find yours use
id user
as below:
  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

 

Application Setup

The webui is at

:8080
and the default username/password is
admin/adminadmin
.

Change username/password via the webui in the webui section of settings.

WEBUI_PORT variable

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=*

Docker Mods

Docker Mods Docker Universal Mods

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.

Support Info

  • Shell access whilst the container is running:
    docker exec -it qbittorrent /bin/bash
  • To monitor the logs of the container in realtime:
    docker logs -f qbittorrent
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' qbittorrent
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/qbittorrent

Updating Info

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:

Via Docker Compose

  • Update all images:
    docker-compose pull
    • or update a single image:
      docker-compose pull qbittorrent
  • Let compose update all containers as necessary:
    docker-compose up -d
    • or update a single container:
      docker-compose up -d qbittorrent
  • You can also remove the old dangling images:
    docker image prune

Via Docker Run

  • Update the image:
    docker pull ghcr.io/linuxserver/qbittorrent
  • Stop the running container:
    docker stop qbittorrent
  • Delete the container:
    docker rm qbittorrent
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
    /config
    folder and settings will be preserved)
  • You can also remove the old dangling images:
    docker image prune

Via Watchtower auto-updater (only use if you don't remember the original parameters)

  • Pull the latest image at its tag and replace it with the same env variables in one run:
    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once qbittorrent
    
  • You can also remove the old dangling images:
    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.

Image Update Notifications - Diun (Docker Image Update Notifier)

  • We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

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
.

Versions

  • 10.02.21: - Rebase to focal.
  • 20.01.21: - Deprecate
    UMASK_SET
    in favor of UMASK in baseimage, see above for more information.
  • 12.11.20: - Stop creating /config/data directory on startup
  • 03.04.20: - Fix adding search engine plugin
  • 02.08.19: - Add qbitorrent-cli for processing scripts.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 14.01.19: - Rebase to Ubuntu, add multi arch and pipeline logic.
  • 25.09.18: - Use buildstage type build, bump qbitorrent to 4.1.3.
  • 14.08.18: - Rebase to alpine 3.8, bump libtorrent to 1.1.9 and qbitorrent to 4.1.2.
  • 08.06.18: - Bump qbitorrent to 4.1.1.
  • 26.04.18: - Bump libtorrent to 1.1.7.
  • 02.03.18: - Bump qbitorrent to 4.0.4 and libtorrent to 1.1.6.
  • 02.01.18: - Deprecate cpu_core routine lack of scaling.
  • 19.12.17: - Update to v4.0.3.
  • 09.02.17: - Rebase to alpine 3.7
  • 01.12.17: - Update to v4.0.2.
  • 27.11.17: - Update to v4 and use cpu_core routine to speed up builds.
  • 16.09.17: - Bump to 3.3.16, Add WEBUI_PORT variable and notes to README to allow changing port of webui.
  • 01.08.17: - Initial Release.
  • 12.02.18: - Initial Release.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.