Anthias runs fewer containers, and its folders are renamed to anthias

Upgrading to Anthias 2026.05.0 changes what runs on the player and where its files live. The installer and the upgrade script make every change for you. This is what you'll see afterward, and what to update if your own scripts or firewall rules depend on the old layout.

Fewer containers

Anthias 0.20.5 ran anthias-server, anthias-viewer, anthias-celery, anthias-websocket, anthias-nginx, anthias-wifi-connect and redis. Anthias 2026.05.0 runs anthias-server, anthias-viewer, anthias-celery and redis, and the upgrade script removes the containers that are gone. anthias-server serves the web interface itself, still on port 80. anthias-celery runs on the anthias-server image, so an upgrade downloads one image fewer.

The Wi-Fi Connect hotspot went with its container.

Folders and files renamed

The folders and files named after Screenly are renamed:

• ~/screenly is now ~/anthias
• ~/screenly_assets is now ~/anthias_assets
• ~/.screenly is now ~/.anthias
• screenly.conf and screenly.db inside it are now anthias.conf and anthias.db

The paths inside anthias.conf are rewritten to match. The old names stay behind as symlinks for now, so cron jobs, backups and scripts that use them keep working, but switch them to the new names.

Only Anthias's own files belong in ~/anthias_assets

Every hour, Anthias deletes any file directly inside ~/anthias_assets that no content item uses, once it's more than an hour old. If you keep other files there, move them somewhere else before you upgrade.

Images come from ghcr.io

The player pulls ghcr.io/screenly/anthias-server, anthias-viewer and anthias-redis instead of the screenly/anthias-* images on Docker Hub. The Docker Hub images are still published as a mirror, but players don't use them. If your network only allows certain registries, allow ghcr.io.

Container logs go to the journal

Each container's logs go to the host's journal instead of Docker's own log files, so they follow the journal's size limits and rotation, and can no longer fill the storage the way a single viewer log file could. Raspberry Pi OS keeps the journal in memory, so these logs don't survive a reboot there. Read them with journalctl -t anthias-server, or with anthias-viewer, anthias-celery or anthias-redis in its place.