Repository navigation
Releases and Upgrades
FischermanCH edited this page May 12, 2026
·
2 revisions
Current public alpha: 0.1.0-alpha251.
ARIA has three update stories. Keep them separate.
This is the preferred public path.
Typical commands:
cd /opt/aria/aria
./aria-stack.sh update
./aria-stack.sh health
./aria-stack.sh logsNormal aria-stack.sh update refreshes/recreates only the aria service. It intentionally leaves Qdrant, SearXNG, Valkey, and volumes alone.
If a release changes the stack layout itself, use:
aria-setup upgrade --install-dir /opt/aria/ariaUse update-all or repair only when release notes or recovery guidance explicitly say so.
Managed installs can also expose the browser update page under /updates.
Normal update:
docker compose -f docker-compose.public.yml pull aria
docker compose -f docker-compose.public.yml up -d --no-deps --force-recreate ariaRules:
- keep the same compose file
- keep the same compose project name
- keep the same volumes
- use host-side Docker commands unless the stack deliberately includes the managed helper
This path is for internal alpha testing:
aria-pulldocker/update-local-aria.shdocker/portainer-stack.alpha3.local.yml- local image
aria:alpha-local
docker/aria-host-update.sh can detect and update Compose-based ARIA stacks.
Main commands:
docker/aria-host-update.sh detectdocker/aria-host-update.sh update --project <name> --dry-rundocker/aria-host-update.sh update --project <name>docker/aria-host-update.sh update --project <name> --target-image fischermanch/aria:<version>
Safety behavior:
- updates only the selected
ariaservice - leaves Qdrant, SearXNG, Valkey, and volumes untouched
- refreshes managed helper files from the target image before recreating ARIA
- preflights the intended host port before recreating ARIA
- aborts safely if another process or container owns that port
aria --versionaria version-check-
/statspreflight -
/updateshelper status on managed installs - browser hard reload after large UI/CSS updates
References: