-
Notifications
You must be signed in to change notification settings - Fork 53
Docker Setup
pyed edited this page Aug 19, 2026
·
1 revision
Running transmission-telegram in Docker is the easiest way to deploy the bot on Linux servers, NAS devices (Synology, TrueNAS, QNAP), unRAID, or Kubernetes.
Here is a complete, production-ready docker-compose.yml integrating Transmission with transmission-telegram:
version: '3.8'
services:
transmission:
image: linuxserver/transmission:latest
container_name: transmission
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- USER=admin
- PASS=secret_password
volumes:
- /path/to/transmission/config:/config
- /path/to/transmission/downloads:/downloads
- /path/to/transmission/watch:/watch
ports:
- "9091:9091"
- "51413:51413"
- "51413:51413/udp"
restart: unless-stopped
telegram-bot:
image: pyed/transmission-telegram:latest
container_name: transmission-telegram
depends_on:
- transmission
restart: unless-stopped
command: >
-token="123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ"
-master="@YourTelegramUsername"
-url="http://transmission:9091/transmission/rpc"
-username="admin"
-password="secret_password"To start the stack:
docker compose up -dIf Transmission is already running:
docker run -d \
--name transmission-telegram \
--restart unless-stopped \
-e TT_BOTT="123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ" \
-e TR_AUTH="admin:secret_password" \
pyed/transmission-telegram:latest \
-master="@YourTelegramUsername" \
-url="http://transmission_ip:9091/transmission/rpc"