July 10Jul 10 I am seeing a Docker update-check issue with a self-hosted Gitea OCI/container registry.Registry/image names:192.168.0.55:3001/vessosa/my-api:latest192.168.0.55:3001/vessosa/my-web:latestWhat works:docker login 192.168.0.55:3001 worksdocker pull 192.168.0.55:3001/vessosa/my-api:latest worksdocker pull 192.168.0.55:3001/vessosa/my-web:latest workscontainers run correctly after manual pull/recreatethe registry is a self-hosted Gitea registry using standard Docker/OCI image supportWhat does not work:Unraid Docker UI shows "not available" for the version/update statusUnraid does not reliably detect whether the local container is up to dateForce Update does not behave like a normal registry update check unless the image was already manually pulled fromCLIExpected behavior:Unraid should support private OCI registries using host:port image references and compare the running container image digest/ID against the remote tag digest. It should show "up-to-date" or "update available" instead of "not available".Possible cause:The image reference contains two ":" characters:192.168.0.55:3001/vessosa/my-api:latestThe first ":" is the registry port.The final ":" is the image tag separator.It looks similar to this older report:https://forums.unraid.net/bug-reports/stable-releases/61210-cant-update-docker-container-with-port-in-url-r2585/That report appears archived/locked, so I am opening a new one with a current reproduction using Gitea. diagnostics-20260710-1523.7z
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.