machsix/transmission repository overview

⁠Fork of linuxserver/docker-transmission

⁠Usage

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

To enable ipv6, follow direction on https://wiki.archlinux.org/index.php/Docker#IPv6⁠. The most important part is to set the correct iptables settings.

The CIDR in /etc/docker/daemon.json is only used for the default bridge network. If you create any network in docker-compose.yaml, you also need to set iptable rule for the specific subnet. For the following case, I specifiy a subnet 2001:db:2::/64. Thus I need the following iptable rule:

ip6tables -t nat -A POSTROUTING -s 2001:db:2::/64 ! -o docker0 -j MASQUERADE

⁠docker-compose

Compatible with docker-compose v2 schemas.

---
version: "3.3"
services:
  transmission:
    image: machsix/transmission:2.94
    container_name: transmission
    environment:
      - PUID=169
      - PGID=169
      - TZ=America/Los_Angeles
        #- TRANSMISSION_WEB_HOME=/combustion-release/ #optional
      - USER=admin #optional
      - PASS=admin #optional
      - UMASK=002
    volumes:
      - /data/Downloads/Transmission/Config:/config
      - /data/Downloads/Transmission/Downloads:/downloads
      - /data/Downloads/Transmission/Incomplete:/incomplete
      - /data/Downloads/Transmission/Watch:/watch
    ports:
      - 9092:9092
      - 51413:51413
      - 51413:51413/udp
    restart: unless-stopped
networks:
  default:
    name: docker-net
    enable_ipv6: true
    ipam:
      driver: default
      config:
        - subnet:  172.22.0.0/24
        - subnet:  2001:db8:2::/64

⁠Parameters

Container images 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.

⁠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

Webui is on port 9091, the settings.json file in /config has extra settings not available in the webui. Stop the container before editing it or any changes won't be saved.

For users pulling an update and unable to access the webui setting you may need to set "rpc-host-whitelist-enabled": false, in /config/settings.json`

If you choose to use transmission-web-control as your default UI, just note that the origional Web UI will not be available to you despite the button being present.

⁠Securing the webui with a username/password.

Use the USER and PASS variables in docker run/create/compose to set authentication. Do not manually edit the settings.json to input user/pass, otherwise transmission cannot be stopped cleanly by the s6 supervisor.

⁠Updating Blocklists Automatically

This requires "blocklist-enabled": true, to be set. By setting this to true, it is assumed you have also populated blocklist-url with a valid block list.

The automatic update is a shell script that downloads a blocklist from the url stored in the settings.json, gunzips it, and restarts the transmission daemon.

The automatic update will run once a day at 3am local server time.