Skip to content

wernight/docker-qbittorrent

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

27 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Docker image for qBittorrent NoX (headless with remote web interface).

Usage

All mounts and ports are optional and qBittorrent will work even with only:

$ docker run wernight/qbittorrent

... however that way some ports used to connect to peers are not exposed, accessing the web interface requires you to proxy port 8080, and all settings as well as downloads will be lost if the container is removed.

So let's create some directories as user 520 (qbittorrent):

$ mkdir config torrents downloads
$ chown 520 config torrents downloads

... and start using this command:

$ docker run -d \
	-p 8080:8080 -p 6881:6881/tcp -p 6881:6881/udp \
	-v $PWD/config:/config \
	-v $PWD/torrents:/torrents \
	-v $PWD/downloads:/downloads \
	wernight/qbittorrent

... to have webUI running on http://localhost:8080 (username: admin, password: adminadmin) with config in the following locations mounted:

  • /config: qBittorrent configuration files
  • /torrents: Torrent files
  • /downloads: Download location

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

You can change 6081 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: 520 was chosen randomly to prevent running as root or as another known user on your system; at least until issue #11253 is fixed.

Feedbacks

Having more issues? Report a bug on GitHub.

Packages

No packages published

Languages

  • Dockerfile 92.5%
  • Shell 7.5%