Chris wrote:
Thanks for the link -- I'll flag it for Tom, and he's already looking into adding unpackerr as an option. On the other part of your question: SparkBox doesn't have a supported way yet to bolt on a brand-new third-party container. There's a power-user overrides system (state/overrides/<module.yml) that lets you tweak settings on apps SparkBox already runs -- like GPU access or memory limits -- and those survive updates, but it's built for adjusting existing containers, not adding new ones. For now your safest route is running unpackerr as its own separate docker-compose stack alongside SparkBox rather than folding it into the box.