November 4Nov 4 A few minutes ago I updated the Handbrake docker. After it updated the Docker screen refreshed and it shows "Not Available" where it would show an update availabe or not - except for Handbrake and one other docker that I updated today. I am on Unraid 7.2.2 and CA Plugin version 2026.07.21 with no updates available.
November 5Nov 5 Updating a container only refreshes the update status of that container. All the other containers keep the result of the last full update check. If that check ran while the server could not reach the registries, for example because of a DNS or internet problem, they all show "not available".Click "Check for Updates" at the bottom of the Docker page and wait for it to finish. Do the statuses come back?If they are still "not available", run these commands on the server and post the output:ping -c 3 registry-1.docker.iocurl -sI https://registry-1.docker.io/v2/Also post the Repository field of two or three of the affected containers, and attach the diagnostics zip (Tools > Diagnostics) taken after the check fails.
18 hours ago18 hr Not 100% related to the thread title, but close. After upgrading from 7.3.4 to 7.4.0, only the containers with a repo to lscr[.]io are showing their update not-available. I am seeing this same issue on all three of my unraid servers. All post upgrade. Before the upgrade, there wasn't an issue. I checked for updates beforehand.Below is the output of the ping and curl, along with a diagnostic from one of my servers. unraid-diagnostics-20261111-0839.zip
18 hours ago18 hr Maybe this? https://forums.unraid.net/topic/201243-unraid-os-740-now-available/#findComment-1641558
17 hours ago17 hr 20 minutes ago, JorgeB said:Maybe this? https://forums.unraid.net/topic/201243-unraid-os-740-now-available/#findComment-1641558YES! That. Thank you. I searched but didn't find anything.Not sure if that is an easy fix I can do, or if it truly does need to be merged and I need to wait for 7.4.1
17 hours ago17 hr 9 minutes ago, UncleStu said:Not sure if that is an easy fix I can doyou can work around it by changing the Repository field in each affected container's template from lscr.io/linuxserver/<app> to ghcr.io/linuxserver/<app>. It's the same image with the same digests, so the container won't really change.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.