Self-host Tdarr with Levelrail

Automated media transcoding, health checks, and library-wide format standardization.

  • AuthorHaveAGitGat
  • LicenceLicenseRef-Tdarr-EULA
  • Memory1 GiB
  • Archarm64
  • Services1

How to self-host Tdarr

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/haveagitgat/tdarr:2.86.01
  2. Create the app

    One service starts in a single Compose app, with 5 named volume mounts for your data, on port 8265.

  3. Fill in the secrets

    9 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Tdarr requirements

Memory
About 1 GiB
Architectures
amd64 image published, arm64 image published
Ports
8265
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
LicenseRef-Tdarr-EULA, proprietary, free to self-host
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 8265 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 Tdarr. 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 Tdarr docs page.

Deploy Tdarr your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Tdarr from the CLI

levelrail-cli templates deploy tdarr --name my-tdarr

Deploy Tdarr with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/tdarr/deploy

Tdarr configuration

Tdarr services

ServiceImagePortsVolumes
tdarr ghcr.io/haveagitgat/tdarr:2.86.01 8265 tdarr_server -> /app/servertdarr_configs -> /app/configstdarr_logs -> /app/logstdarr_media -> /mediatdarr_transcode_cache -> /temp

Tdarr environment variables

VariableServiceValue
PGID tdarr Preset by the template
PUID tdarr Preset by the template
TZ tdarr Preset by the template
ffmpegVersion tdarr Preset by the template
inContainer tdarr Preset by the template
internalNode tdarr Preset by the template
serverIP tdarr Preset by the template
serverPort tdarr Preset by the template
Show all 9 variables
  • webUIPorttdarrPreset by the template

Ports and volumes

Ports
8265
Volumes
5 named mounts: tdarr_server -> /app/server, tdarr_configs -> /app/configs, tdarr_logs -> /app/logs, tdarr_media -> /media, tdarr_transcode_cache -> /temp

Tdarr FAQ

How much memory does Tdarr need?

The catalog lists about 1 GiB of memory for Tdarr.

Does Tdarr run on arm64?

For Tdarr, an arm64 image is published; amd64 is image published.

What licence is Tdarr under?

Tdarr is licensed under LicenseRef-Tdarr-EULA, which is proprietary, so check the vendor terms.

Does Tdarr need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Tdarr use?

Tdarr listens on port 8265 inside the stack.

Where does Tdarr keep its data?

In named volumes: tdarr_server mounted at /app/server, tdarr_configs mounted at /app/configs, tdarr_logs mounted at /app/logs and tdarr_media mounted at /media.

Can I deploy Tdarr 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 Tdarr, 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 ghcr.io/haveagitgat/tdarr:2.86.01 is what you deploy there.

levelrail-cli templates deploy tdarr --name my-tdarr