All-jellyfin-media-server tested by Argusic Runner

What the test found

The repo's installer-script configuration phase works end to end (state saved, dirs created, compose templates downloaded), and all eight stack services (Jellyfin 12.2, Jellyseerr 3.5.0, Sonarr, Radarr, Prowlarr, Jackett, qBittorrent 5.2.4, FlareSolverr 3.5.2) run from official upstream releases in this container and answer their documented HTTP/API endpoints with real 2xx responses, with the caveat that the Docker Compose deployment itself could not be exercised because this container provides no Docker daemon and no namespace privileges.

Setup script itself runs to completion and creates all config/dirs (PACK_TYPE=1, COMMON_PATH written, compose templates downloaded byte-identical); the Docker deployment step is impossible in this container (no root, namespaces blocked). Real upstream binaries of all 8 services were launched and exercised over HTTP/API in place of Docker: Jellyfin 12.2 (login 200, libraries 204), Jellyseerr 3.5.0 (built from repo source, /setup 200), Sonarr 4.0.20 (status 200, rootfolder 201), Radarr 6.4.4 (status 200, rootfolder 201), Prowlarr 2.6.5 (status 200, FlareSolverr+Sonarr+Radarr apps 201), qBittorrent 5.2.4 (login 204, categories 200), Jackett 0.24 (dashboard 200, indexer JSON list 200), FlareSolverr 3.5.2 (sessions.list 200 after supplying missing libwayland-server.so.0). Jellyfin requires the Authorization header format; legacy X-Emby headers only work after manually enabling EnableLegacyAuthorization.

Argusic could not fully install All-jellyfin-media-server and launched it; verification reached Verified running for real. 7 of 7 recorded errors were worked through (see the timeline below).

Did not runall runs of All-jellyfin-media-server

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.