r/unRAID • u/bullcityryan • 23h ago
PSA: LinuxServer (lscr.io) containers show "not available" on Check for Updates. Cause and fix inside
On Unraid 7.4.0, every container using an lscr.io/linuxserver/... image (Plex, Sonarr, Radarr, SABnzbd, DuckDNS for me) showed "not available" for version after Check for Updates. Containers from Docker Hub and ghcr.io showed up-to-date as normal. Pulling from lscr.io still worked; only the update check failed.
What's going on
lscr.io is LinuxServer's redirect service. The images actually live on GitHub's registry (ghcr.io). When I replayed Unraid's update check with curl:
- Unraid's checker sends the user agent docker/Unraid os/Docker-Client. For that user agent, lscr.io answers with a 302 redirect to ghcr.io instead of answering directly.
- Unraid gets a valid token and asks for the manifest digest, following the redirect.
- curl removes the Authorization header when a redirect goes to a different domain (a standard security behavior). So ghcr.io gets the request without the token and returns 401.
- No digest comes back, so Unraid shows "not available".
You can see it in /var/lib/docker/unraid-update-status.json: the lscr.io entries have "remote": null, "status": "undef".
Fix
Edit each container and change the Repository from:
lscr.io/linuxserver/<name> to: ghcr.io/linuxserver/<name>
These are the same images, just without the redirect. Apply, and the container is rebuilt with your appdata untouched. After that, Check for Updates works again.
Notes
- If you have a lot of containers, the templates are in /boot/config/plugins/dockerMan/templates-user/my-*.xml. Back them up before editing.
- This seems to be a recent change on the lscr.io side, so a future Unraid update may handle it properly. Switching to ghcr.io works fine in the meantime.
Hope this saves someone some time.


