tomspark wrote:
Good idea, noted — I'll add it to the backlog. You're right that qBittorrent's image doesn't ship unrar, and unpackerr handles the whole extraction + cleanup workflow that most arr-stack users end up needing anyway. Pre-configured in the media bundle would save people the manual setup you just did. Thanks for the push on this one.
skylyn wrote:
How did you get unpackerr running? I have installed it and configured it with proper keys, but logs say it's unable to find the downloads. This is because it's looking at /data/downloads, but my downloads are actually in /mnt/media/downloads. I believe there's a configuration for the media stack that points /data to /mnt/media, but unpackerr seems to be missing that configuration.
Chris wrote:
You have diagnosed it exactly right, and the mapping you suspected is real. Every media container SparkBox builds gets your media root bind-mounted in as /data — so inside Sonarr, Radarr and qBittorrent, /data IS your /mnt/media. That is why they all report /data/downloads while the files genuinely live at /mnt/media/downloads. Nothing is misconfigured; you are just seeing the inside-the-container view. Your unpackerr is running outside that arrangement, so it needs the same mount to make those paths line up: give it /mnt/media mounted at /data, and its config can keep using the /data/downloads paths the arr apps hand it. Pointing unpackerr at /mnt/media/downloads instead works too, as long as it matches what you told it. Still no unpackerr module, so this stays manual for now. — Chris