Self-host Transmission with Levelrail
A fast, lightweight BitTorrent client with a simple web interface.
- Authortransmission
- LicenceGPL-2.0-only OR GPL-3.0-only
- Memory256 MiB
- Archarm64
- Services1
How to self-host Transmission
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/transmission:4.0.6
-
Create the app
One service starts in a single Compose app, with 3 named volume mounts for your data, on port 9091.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Transmission requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 9091
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-2.0-only OR GPL-3.0-only, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 9091 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Transmission. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Transmission docs page.
Deploy Transmission your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Transmission from the CLI
levelrail-cli templates deploy transmission --name my-transmission Deploy Transmission with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/transmission/deploy Transmission configuration
Transmission services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| transmission | lscr.io/linuxserver/transmission:4.0.6 | 9091 | transmission_config -> /configtransmission_downloads -> /downloadstransmission_watch -> /watch |
Transmission environment variables
| Variable | Service | Value |
|---|---|---|
| PASS | transmission | Generated at deploy |
| PGID | transmission | Preset by the template |
| PUID | transmission | Preset by the template |
| USER | transmission | Generated at deploy |
Ports and volumes
- Ports
- 9091
- Volumes
- 3 named mounts: transmission_config -> /config, transmission_downloads -> /downloads, transmission_watch -> /watch
Transmission FAQ
How much memory does Transmission need?
The catalog lists about 256 MiB of memory for Transmission.
Does Transmission run on arm64?
For Transmission, an arm64 image is published; amd64 is image published.
What licence is Transmission under?
Transmission is licensed under GPL-2.0-only OR GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does Transmission need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Transmission use?
Transmission listens on port 9091 inside the stack.
Where does Transmission keep its data?
In named volumes: transmission_config mounted at /config, transmission_downloads mounted at /downloads and transmission_watch mounted at /watch.
Can I deploy Transmission on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Transmission, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/transmission:4.0.6 is what you deploy there.