Updates
Use alpha for the moving early-access channel or a versioned tag for a repeatable deployment:
STACKARR_IMAGE=polyphonic/stackarr:alphaUpdate from Stackarr
Stackarr separates controller updates from the apps it manages. This keeps an unavailable or locally built Stackarr image from blocking updates for Plex, the Arr apps, download clients, and the rest of the enabled stack.
Ask an admin-profile agent to back up and update the managed apps, use System → Updates → Update apps, or run:
docker exec app /app/bin/stackarr update servicesThe app workflow targets managed services explicitly, leaves the Stackarr controller and its database running, reapplies integrations, and cleans up dangling and unused images. Cleanup runs after Compose has recreated the services and removed old containers, so images from the previous containers are no longer referenced. The scheduled update job uses this same workflow.
Persistent Docker volumes are not pruned automatically. First use
stackarr_get_container_overview to review every unused volume. After confirming
that a specific volume's data is no longer needed, call
stackarr_remove_docker_volume with its exact name as id,
confirmDangerous: true, and a reason. Repeat for each reviewed volume. Stackarr
rejects bulk volume pruning so the confirmation cannot sweep up unrelated
volumes that became unused later.
When an older RomM or FlareSolverr container still uses an image-declared anonymous volume, the next managed Compose reconciliation copies its data into the new stable named volume and verifies the copy before recreation. The original volume is retained for manual review; remove it only after the recreated service is healthy and its data is present.
Stackarr defaults application services such as Youtarr and tinyMediaManager to their upstream stable moving tags so this workflow keeps them current. Stateful infrastructure such as database engines stays version-pinned when an automatic major upgrade could break persisted data or configuration. Every image remains runtime-configurable when an installation needs a deliberate version pin.
Update only the Stackarr app
Use System → Updates → Update Stackarr, or run:
docker exec app /app/bin/stackarr update appThe running controller hands this operation to a one-shot maintenance worker. That worker pulls only the Stackarr image, reconciles database access, recreates only the controller, waits for its health endpoint, and records the result in Activity. Other services stay online.
When STACKARR_IMAGE ends in :local, Stackarr keeps that image and explains
that it must be rebuilt from its source checkout. Managed app updates still run
normally.
The legacy stackarr update run command remains an alias for
stackarr update services.