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/deluge

Deluge is a lightweight, Free Software, cross-platform BitTorrent client.

• Full Encryption
• WebUI
• Plugin System
• Much more...

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/deluge:latest 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	Available	Tag
x86-64	✅	amd64-<version tag>
arm64	✅	arm64v8-<version tag>
armhf	❌

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.

Tag	Available	Description
latest	✅	Stable Deluge releases
libtorrentv1	✅	Stable Deluge releases using libtorrentv1

Application Setup

The admin interface is available at http://SERVER-IP:8112 with a default user/password of admin/deluge.

To change the password (recommended) log in to the web interface and go to Preferences->Interface->Password.

Change the inbound port to 6881 (or whichever port you've mapped for the container) under Preferences->Network, otherwise random ports will be used.

Read-Only Operation

This image can be run with a read-only container filesystem. For details please read the docs.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

docker-compose (recommended, click here for more info)

---
services:
  deluge:
    image: lscr.io/linuxserver/deluge:latest
    container_name: deluge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - DELUGE_LOGLEVEL=error #optional
    volumes:
      - /path/to/deluge/config:/config
      - /path/to/downloads:/downloads
    ports:
      - 8112:8112
      - 6881:6881
      - 6881:6881/udp
      - 58846:58846 #optional
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=deluge \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e DELUGE_LOGLEVEL=error `#optional` \
  -p 8112:8112 \
  -p 6881:6881 \
  -p 6881:6881/udp \
  -p 58846:58846 `#optional` \
  -v /path/to/deluge/config:/config \
  -v /path/to/downloads:/downloads \
  --restart unless-stopped \
  lscr.io/linuxserver/deluge:latest

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> 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 8112	Port for webui
-p 6881	Inbound torrent traffic (See App Setup)
-p 6881/udp	Inbound torrent traffic (See App Setup)
-p 58846	Default deluged port for thin client connectivity
-e PUID=1000	for UserID - see below for explanation
-e PGID=1000	for GroupID - see below for explanation
-e TZ=Etc/UTC	specify a timezone to use, see this list.
-e DELUGE_LOGLEVEL=error	set the loglevel output when running Deluge, default is info for deluged and warning for delgued-web
-v /config	deluge configs
-v /downloads	torrent download directory
--read-only=true	Run container with a read-only filesystem. Please read the docs.

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__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable 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 your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker 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 deluge /bin/bash

• To monitor the logs of the container in realtime:

  docker logs -f deluge

• Container version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' deluge

• Image version number:

  docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/deluge:latest

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 (noted in the relevant readme.md), 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 images:

  • All images:

    docker-compose pull

  • Single image:

    docker-compose pull deluge

• Update containers:

  • All containers:

    docker-compose up -d

  • Single container:

    docker-compose up -d deluge

• You can also remove the old dangling images:

  docker image prune

Via Docker Run

• Update the image:

  docker pull lscr.io/linuxserver/deluge:latest

• Stop the running container:

  docker stop deluge

• Delete the container:

  docker rm deluge

• 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

Image Update Notifications - Diun (Docker Image Update Notifier)

Tip

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-deluge.git
cd docker-deluge
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/deluge: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

• 19.09.24: - Prevent race condition related delay during container stop.
• 26.08.24: - Add libtorrentv1 tag.
• 26.12.23: - Replace source for GeoIP database.
• 07.12.23: - Add optional port 58846 to readme for thin client connectivity.
• 07.10.23: - Install unrar from linuxserver repo.
• 10.08.23: - Bump unrar to 6.2.10.
• 30.06.23: - Bump unrar to 6.2.8, deprecate armhf as per https://www.linuxserver.io/armhf.
• 29.11.22: - Restore geoip using py3-geoip as an interim measure.
• 24.11.22: - Remove GeoIP packages as geoip will not build under Py 3.11 and Deluge still doesn't support geoip2.
• 22.11.22: - Update GeoIP URL for new IPFS domain.
• 29.08.22: - Rebase to Alpine Edge again to follow latest releases.
• 12.08.22: - Bump unrar to 6.1.7.
• 16.06.22: - Rebase to Alpine 3.16 from edge.
• 22.02.22: - Rebase to Alpine, config on first startup, add GeoIP.
• 15.01.22: - Rebase to Focal.
• 07.06.21: - Remove host networking from readme examples
• 23.01.21: - Deprecate UMASK_SET in favor of UMASK in baseimage, see above for more information.
• 09.05.19: - Add python3 requests and future modules.
• 24.08.19: - Add ability to set LogLevel for Deluge.
• 09.06.19: - Update to 2.x using deluge ppa.
• 02.05.19: - Install full version of 7zip.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 15.11.18: - Add deluge-console.
• 11.11.18: - Rebase to Ubuntu Bionic, add pipeline multiarch logic.
• 09.04.18: - update to libressl2.7-libssl.
• 29.03.18: - Rebase to alpine edge.
• 07.12.17: - Rebase to alpine 3.7.
• 20.11.17: - Change libressl2.6-libssl repo.
• 01.07.17: - Add curl package.
• 26.05.17: - Rebase to alpine 3.6.
• 29.04.17: - Add variable for user defined umask.
• 28.04.17: - update to libressl2.5-libssl.
• 28.12.16: - Rebase to alpine 3.5 baseimage.
• 17.11.16: - Rebase to edge baseimage.
• 13.10.16: - Switch to libressl as openssl deprecated from alpine linux and deluge dependency no longer installs
• 30.09.16: - Fix umask.
• 09.09.16: - Add layer badges to README.
• 30.08.16: - Use pip packages for some critical dependencies.
• 28.08.16: - Add badges to README.
• 15.08.16: - Rebase to alpine linux.
• 09.11.15: - Add unrar and unzip
• 15.10.15: - Initial Release.