专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

80x86/qbittorrent Docker 镜像 - 轩辕镜像

qbittorrent
80x86/qbittorrent
[v4.6.0] amd64/arm64(aarch64) / auto https(ACME) / Log viewer
209 收藏0 次下载
🔒 更安全的专业镜像服务
镜像简介版本下载
🔒 更安全的专业镜像服务

the latest stable version is 4.6.0-39-minimal-amd64-full

tag name with nova has been renamed to full ( full means has builtin python3 support for qb torrent search engine)

the old version tag name with nova means has python3 support (for qb torrent search engine), now it is full

tagdescription
4.6.0-39-minimal-amd64-fullbased on fedora minimal image, builtin Python
4.6.0-39-minimal-amd64based on fedora minimal image, no Python

featured qBittorrent-nox for container

!80x86/qbittorrent pull stats

bash
[***]

qBittorrent NoX is the headless with remote web interface version of qBittorrent BitTorrent client.

changelog

*20231028: update to qb 4.6.0

  • 20200325: new version qb 4.2.2, default https, automatic HTTPS support via ACME added

  • 20191219: new version qb 4.2.1

  • 20191209: new version qb 4.2.0 (with new tag: 4.2.0 , not latest)

  • auto category feature added, for old container, you can setup "Run external program on torrent completion" to /usr/local/bin/qb-auto-cat -h %I in qb WEB UI

  • 20191115: rollback to qb 4.1.9 due to version number problem (some PT only allow qb 4.X.X version)

  • 20191113: upgraded to qb 4.1.9.1

  • 20190829: fixup js memory leak in log tab


Feature

  1. Automatic HTTPS support via ACME
  2. Automatic categorization torrent based on tracker hostname (Private Trackers only)
  3. Automatic tagging not working torrent to special tag 0xDEADBEEF
  4. Log viewer added to the WEB UI
  5. Optimized WEB UI based on usage experience

attention

  1. this container is SSL default but you can change to http in the WEB UI.

    you need to remove the cookie named SID in your browser after the protocol changed.

  2. no latest tag !!! use specific tag please

    the examples below uses 4.4.2-amd64 as the tag,

    in the real world, you should always check and use the newest available tag

  3. do not just copy and paste the sample commands below

    you need to modify the commands for your needs!

  4. change tag from xxx-amd64 to xxx-arm64 if you are on a aarch64/arm64 machine


volume must map

containerdescription
/configdir to save qBittorrent configuration files
/datadir to save qBittorrent data (include BT_backup directory which stored torrents)
/downloadsqBittorrent default download location

env var

namedefault valuedescription
PUID1000run as uid
PGID100run as gid
UMASK_SET000umask for app running user
WEB_PORT8080http or https listen port
BT_PORT8999BT listen port (both tcp and udp)
QBT_GEOIP_DB_URLURL for downloading GeoLite2-Country.mmdb.gz
FB_AUTH_SERVER_ADDR127.0.0.1dashboard IP, for auto authenticate with dashboard

config file path

config file/dircontainerdescription
qBittorrent.conf/config/qBittorrent.confconfig file
qBittorrent-data.conf/config/qBittorrent-data.confstats data file
ssl.crt/config/ssl.crtSSL certificate
ssl.key/config/ssl.keySSL private key
rss/feeds.json/config/rss/feeds.jsonRSS feeds
BT_backup/data/BT_backup.torrent and .fastresume files goes here
GeoLite2-Country.mmdb/data/GeoIP/GeoLite2-Country.mmdb
*.py/data/nova3/engines/nova3 search engine plugins
/data/rss/articles/RSS articles data
qbittorrent.log/data/logs/qbittorrent.loglog file

How to use this image

This image is:

  • Small: :latest is based on official Alpine Docker image.
  • Simple: Exposes correct ports, configured for remote access...
Usage

start it using this command:

bash
    $ WEB_PORT=8082
    $ BT_PORT=8999
    $ mkdir -p config data downloads
 $ podman run -d --name qbittorrent \
  -e PUID=$UID \
  -e PGID=$GID \
  -e WEB_PORT=8082 \
  -e BT_PORT=8999 \
  --restart=always \
  -p $WEB_PORT:$WEB_PORT -p $BT_PORT:$BT_PORT/tcp -p $BT_PORT:$BT_PORT/udp \
  -v $PWD/config:/config \
  -v $PWD/data:/data \
  -v $PWD/downloads:/downloads \
  80x86/qbittorrent:4.2.2-amd64

... to run as yourself and have WebUI running on https://localhost:8082 (username: admin, password: adminadmin) with config in the following locations mounted:

  • /config: qBittorrent configuration files
  • /data: qBittorrent data directory(include BT_backup directory which stored torrents)
  • /downloads: Download location

Note: By default it runs as UID 2048 and GID 2048, but can run as any user/group.

It is probably a good idea to add --restart=always so the container restarts if it goes down.

You can change 8999 to some random port number (also change in the settings).

Note: For the container to run, the legal notice had to be automatically accepted. By running the container, you are accepting its terms. Toggle the flag in qBittorrent.conf to display the notice again.

Note: 2048 was chosen randomly to prevent running as root or as another known user on your system; at least until issue #*** is fixed.


How to Enable Automatic HTTPS via ACME (let's encrypt by default)

take cloudflare for example, your need add following env vars:

bash
-e AUTOCERT_EMAIL=your-email-for-acme \
-e AUTOCERT_DOMAIN=you-domain.com \
-e AUTOCERT_DNS_PROVIDER=cloudflare \
-e CF_DNS_API_TOKEN="your-cf-token-here" \

an full example:

bash
$ WEB_PORT=8082
$ BT_PORT=8999
$ mkdir -p config data downloads
$ podman run -d --name qbittorrent \
 -e PUID=$UID \
 -e PGID=$GID \
 -e WEB_PORT=8082 \
 -e BT_PORT=8999 \
 -e AUTOCERT_EMAIL=*** \
 -e AUTOCERT_DOMAIN=you-domain.com \
 -e AUTOCERT_DNS_PROVIDER=cloudflare \
 -e CF_DNS_API_TOKEN="your-cf-token-here" \
 --restart=always \
 -p $WEB_PORT:$WEB_PORT -p $BT_PORT:$BT_PORT/tcp -p $BT_PORT:$BT_PORT/udp \
 -v $PWD/config:/config \
 -v $PWD/data:/data \
 -v $PWD/downloads:/downloads \
 80x86/qbittorrent:4.2.2-amd64

attenion: change $PWD/config ... to your own path, DO NOT copy and paste!

bash
# ACME related env vars
# acme check interval in hours, default to 24 hours
GO_ACME_INTERVAL=24

# change CA server to `[***]` if you want to test
GO_ACME_CA_SERVER=""

# set to [***] if you want to use http proxy for ACME
HTTP_PROXY=""
AUTOCERT_EMAIL=""

# ACME domain like `foo.com`, can be multi like `foo.com,b.bar.com`, can be wildcard like `*.foo.com`
AUTOCERT_DOMAIN=""

# must be one of `RSA2048`, `RSA4096`, `RSA8192`, `EC256`, `EC384`  
AUTOCERT_KEYTYPE=EC256

# ACME DNS provider, default is cloudflare
AUTOCERT_DNS_PROVIDER=cloudflare

# this env var is only used by `cloudflare` DNS provider
CF_DNS_API_TOKEN=""

ACME additional env var for DNS provider

availabel DNS providers
bash
alidns,azure,cloudflare,cloudxns,digitalocean,dnspod,gcloud,linodev4,namecheap,qcloud,rfc2136,vultr

cloudflare:

get token from "My Profile -> API Tokens" API token must include the following permissions: Zone.Zone: Read Zone.DNS: Edit Zone Resources: All zones

Environment Variable Namedescription
CF_DNS_API_TOKENAPI Token

dnspod:

Environment Variable Namedescription
DNSPOD_API_KEYformat is: id,token

qcloud:

Environment Variable Namedescription
QCLOUD_SECRET_IDThe SecretId
QCLOUD_SECRET_KEYThe SecretKey

alidns:

Environment Variable Namedescription
ALICLOUD_ACCESS_KEYAccess key ID
ALICLOUD_SECRET_KEYAccess Key secret

for other provider please ref to: <[***]>

ACME Testing

To test or experiment with your configuration,

make sure you change the ACME endpoint to a staging or development URL,

otherwise you are likely to hit rate limits which can block your access to HTTPS for up to a week,

depending on which rate limit you hit.

the default CA is Let's Encrypt, which has a staging endpoint that is not subject to the same rate limits:

bash
[***]

you can set it for your container by using env var

GO_ACME_CA_SERVER="[***]"


more detailed example
use bridged network
shell
# begin config
WEB_PORT=http listen port
DOWNLOAD_PATH="download dir"
BT_PORT=bt incoming port
CFG_PATH="config dir"
DATA_PATH="data dir"
RUN_USER="qbittorrent"
# end config

IMAGE_NAME=80x86/qbittorrent:4.2.2-amd64
QBT_AUTH_SERVER_ADDR=$(ip -4 addr show docker0 | grep inet | awk '{print $2}' | cut -d'/' -f1)
podman run -d --name qbittorrent \
        -e PUID=$(id -u $RUN_USER) \
  -e PGID=$(id -g $RUN_USER) \
        -e WEB_PORT=$WEB_PORT \
        -e BT_PORT=$BT_PORT \
        -e QBT_AUTH_SERVER_ADDR=$QBT_AUTH_SERVER_ADDR \
        --restart unless-stopped \
        -p $WEB_PORT:$WEB_PORT -p $BT_PORT:$BT_PORT/tcp -p $BT_PORT:$BT_PORT/udp \
        -v "$CFG_PATH":/config \
        -v "$DATA_PATH":/data \
        -v "$DOWNLOAD_PATH":/downloads \
        --mount type=tmpfs,destination=/tmp \
        ${IMAGE_NAME}

use hosted network

shell
# begin config
WEB_PORT=http listen port
DOWNLOAD_PATH="download dir"
BT_PORT=bt incoming port
CFG_PATH="config dir"
DATA_PATH="data dir"
RUN_USER="qbittorrent"
# end config

IMAGE_NAME=80x86/qbittorrent:4.2.2-amd64
QBT_AUTH_SERVER_ADDR="127.0.0.1"
podman run -d --name qbittorrent \
        -e PUID=$(id -u $RUN_USER) \
  -e PGID=$(id -g $RUN_USER) \
        -e WEB_PORT=$WEB_PORT \
        -e BT_PORT=$BT_PORT \
        -e QBT_AUTH_SERVER_ADDR=$QBT_AUTH_SERVER_ADDR \
        --restart unless-stopped \
        --network host \
        -v "$CFG_PATH":/config \
        -v "$DATA_PATH":/data \
        -v "$DOWNLOAD_PATH":/downloads \
        --mount type=tmpfs,destination=/tmp \
        ${IMAGE_NAME}

for NanoDM users
NanoDM migration: use bridged network
shell
IMAGE_NAME=80x86/qbittorrent:4.2.2-arm64
WEB_PORT=$(nvram get app.qb.listen_port)
DOWNLOAD_PATH=$(cat /var/lib/qbittorrent/.config/qBittorrent/qBittorrent.conf | grep -i 'Downloads\\SavePath' | cut -d'=' -f2)
BT_PORT=$(cat /var/lib/qbittorrent/.config/qBittorrent/qBittorrent.conf | grep -i 'Connection\\PortRangeMin' | cut -d'=' -f2)
QBT_AUTH_SERVER_ADDR=$(ip -4 addr show docker0 | grep inet | awk '{print $2}' | cut -d'/' -f1)
if [ "$DOWNLOAD_PATH" = "/downloads" ] || [ "$DOWNLOAD_PATH" = "/downloads/" ]; then
 echo "please set correct DOWNLOAD_PATH"
 exit -1
fi
podman run -d --name qbittorrent \
  -e PUID=$(id -u qbittorrent) \
  -e PGID=$(cat /etc/group | grep -e '^users' | cut -d':' -f3) \
  -e WEB_PORT=$WEB_PORT \
  -e BT_PORT=$BT_PORT \
  -e QBT_AUTH_SERVER_ADDR=$QBT_AUTH_SERVER_ADDR \
  --restart unless-stopped \
  -p $WEB_PORT:$WEB_PORT -p $BT_PORT:$BT_PORT/tcp -p $BT_PORT:$BT_PORT/udp \
  -v /var/lib/qbittorrent/.config/qBittorrent:/config \
  -v /var/lib/qbittorrent/.local/share/data/qBittorrent:/data \
  -v "$DOWNLOAD_PATH":/downloads \
  --mount type=tmpfs,destination=/tmp \
  ${IMAGE_NAME}
NanoDM migration: use hosted network
shell
IMAGE_NAME=80x86/qbittorrent:4.2.2-arm64
WEB_PORT=$(nvram get app.qb.listen_port)
DOWNLOAD_PATH=$(cat /var/lib/qbittorrent/.config/qBittorrent/qBittorrent.conf | grep -i 'Downloads\\SavePath' | cut -d'=' -f2)
BT_PORT=$(cat /var/lib/qbittorrent/.config/qBittorrent/qBittorrent.conf | grep -i 'Connection\\PortRangeMin' | cut -d'=' -f2)
QBT_AUTH_SERVER_ADDR="127.0.0.1"
if [ "$DOWNLOAD_PATH" = "/downloads" ] || [ "$DOWNLOAD_PATH" = "/downloads/" ]; then
 echo "please set correct DOWNLOAD_PATH"
 exit -1
fi
podman run -d --name qbittorrent \
  -e PUID=$(id -u qbittorrent) \
  -e PGID=$(cat /etc/group | grep -e '^users' | cut -d':' -f3) \
  -e WEB_PORT=$WEB_PORT \
  -e BT_PORT=$BT_PORT \
  -e QBT_AUTH_SERVER_ADDR=$QBT_AUTH_SERVER_ADDR \
  --restart unless-stopped \
  --network host \
  -v /var/lib/qbittorrent/.config/qBittorrent:/config \
  -v /var/lib/qbittorrent/.local/share/data/qBittorrent:/data \
  -v "$DOWNLOAD_PATH":/downloads \
  --mount type=tmpfs,destination=/tmp \
  ${IMAGE_NAME}

Image Variants

80x86/qbittorrent:<version>

Those are tagged versions built from source code.

based on Alpine Linux

User Feedbacks

Having more issues? Report a bug on GitHub.

查看更多 qbittorrent 相关镜像 →
linuxserver/qbittorrent logo
linuxserver/qbittorrent
这是由LinuxServer.io提供的Qbittorrent容器,Qbittorrent作为一款开源、轻量且功能全面的BitTorrent客户端,支持跨平台运行,具备强大的种子管理、下载调度及远程控制功能;该容器化部署方案便于用户快速搭建、高效管理,适用于家庭服务器、NAS设备或企业级存储环境,为文件共享与下载任务提供稳定可靠的运行环境。
1631100M+ pulls
上次更新:未知
kasmweb/qbittorrent logo
kasmweb/qbittorrent
qBittorrent for Kasm Workspaces
26100K+ pulls
上次更新:未知
crazymax/qbittorrent logo
crazymax/qbittorrent
基于Alpine Linux的qBittorrent Docker镜像,提供轻量级、高效的开源BitTorrent客户端服务,适用于BT下载与管理。
111M+ pulls
上次更新:未知
wernight/qbittorrent logo
wernight/qbittorrent
Lightweight qBittorrent-NoX (i.e. headless) torrent client and one of the most feature complete
601M+ pulls
上次更新:未知
emmercm/qbittorrent logo
emmercm/qbittorrent
Headless qBittorrent client with remote web interface.
4100K+ pulls
上次更新:未知
p3terx/qbittorrent logo
p3terx/qbittorrent
qBittorrent Enhanced Edition
2950K+ pulls
上次更新:未知

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

专属域名拉取

无需登录使用专属域名

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

轩辕镜像免费版与专业版有什么区别?

免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。

轩辕镜像支持哪些镜像仓库?

专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。

流量耗尽错误提示

当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。

镜像拉取成功后,如何去掉轩辕镜像域名前缀?

使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
80x86/qbittorrent
官方博客Docker 镜像使用技巧与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
咨询镜像拉取问题请 提交工单,官方技术交流群:1072982923
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
咨询镜像拉取问题请提交工单,官方技术交流群:
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
官方邮箱:点击复制邮箱
©2024-2026 源码跳动
官方邮箱:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.