Tdarr cache
Posted by simplebenn
Via tom AI: Issue: No way to bind a separate cache volume into Tdarr — forced to share volume1 with the media library Setup: media library on volume1 (MEDIAROOT), a separate SSD pool on volume2 intended for Tdarr's transcode cache/scratch space. Tdarr's compose only mounts MEDIAROOT → /data. There's no second bind mount or env var (e.g. TDARRCACHEROOT) wiring an SSD/scratch volume into the container. Workaround in use: cache path set to /data-adjacent (volume1) since that's the only volume actually present inside the container — meaning transcode scratch I/O hits the same disk as the library, not the SSD, defeating the purpose of having a separate fast pool. Ask: add a second configurable bind (env-driven, e.g. TDARRCACHEROOT → /cache) to modules/tdarr/docker-compose.yml so cache can live on a different volume/pool than the library, same pattern as MEDIAROOT.
2 replies
Chris wrote:
Good catch, and actually the cache isn't sharing your media library's disk today — it lives in its own folder (separate from MEDIAROOT). So there's already a lever here: point SBDATADIR at your SSD pool in the SparkBox .env file, and set MEDIAROOT to keep the library on volume1. That puts Tdarr's cache (and a couple other odds and ends) on the fast drive without touching the library. Not quite as clean as a dedicated cache-only setting though, so I've logged the ask for a proper env knob with Tom.
tomspark wrote:
Heads up — 1.6.496 just shipped and should cover what you reported here. You can grab it straight from the dashboard: Settings → Updates → Update SparkBox. Let me know if that sorts it, or if you're still hitting it. (Prefer the terminal? sudo sparkbox upgrade — note update only refreshes app images and will not move you to a new release.)