obsidian-vault/family/how-to/arr-stack-taiga.md

title, created, updated, type, namespace, tags, related

title	created	updated	type	namespace	tags	related
Arr Stack — Taiga	2026-05-23	2026-09-02	tech	family	arr taiga infra media pitfalls	tech/arr-stack-kraken

Arr Stack — Taiga

Secondary arr stack on Taiga (TrueNAS), added 2026-05-20.

STATE 2026-09-02: Стек выключен — в docker ps -a нет ни radarr/sonarr/prowlarr/jellyfin контейнеров (стек не пересоздавался). Compose-структура живёт в /mnt/RED_2TB/docker/arr/ (docker-compose.yml + подпапки prowlarr/ radarr/ sonarr/ jellyfin/ media-pipeline/). Работает только transmission (отдельный compose /mnt/RED_2TB/docker/transmission/).

Почему не запускается просто так — медиа-права сломаны (тот же restore-инцидент uid 921/0000): /mnt/RED_2TB/storage/{Movies,Cartoons,Downloads,Music,series,shared} → d---------/drwx------, owner transmission (uid 921). radarr/sonarr монтируют /storage (rw), jellyfin :ro — со сломанными правами не прочитают библиотеку. Фикс + запуск: см. family/documents/vault-sync/2026-09-02-restore-privilege-scope.md.

Docker-image facts (2026-09-02): All 5 media images loaded locally on TrueNAS (docker images): lscr.io/linuxserver/{radarr,sonarr,jellyfin,transmission,prowlarr}:latest. Only transmission container exists (running). jellyfin/radarr/sonarr/prowlarr containers are NOT yet created — they never get launched until perms fixed. Transmission runs as ROOT (not 911/950): its compose /mnt/RED_2TB/docker/transmission/docker-compose.yml has no PUID/PGID, so linuxserver /init (s6-overlay) leaves it root (docker exec transmission id → uid 0). This is why it works on the 0000 media dirs. It mounts storage → /mnt/storage, download-dir = /mnt/storage/Downloads. Fix direction (approved Variant A): set PUID=950 PGID=950 on transmission + all arr/jellyfin compose services so every service shares uid 950 and mutually reads files; then recursively fix perms in depth. Plan + commands: 2026-09-02-restore-privilege-scope.md §5.

Notes from Setup (2026-05-20)

• Config and pitfalls recorded during initial Taiga arr stack deployment
• router.py was customized — check /mnt/RED_2TB/docker/arr-taiga/router.py for current state

Key Differences from Kraken Stack

• Taiga = TrueNAS host (storage-focused)
• Kraken = Raspberry Pi 5 (playback-focused)
• Taiga stack handles acquisition; Kraken handles serving to Jellyfin

Pitfalls

(Details were referenced but not captured. Update this page after next Taiga arr maintenance session.)