Hi,
Â
Today I added a Docker Container that is on a custom Container Registry and not on DockerHub.
The Registry is a Gitlab Registry hosted by my University.
I've added the login credentials via the CLI and it worked without problems. I could add the Docker Container in the GUI and Unraid pulled and started it (almost) normally.
I immediately noticed that on the Docker Page that for the container it showed "not available" for the version. So I made an update to the docker image (I'm pushing the updates so I know that there is one available), and tried to force the update via the advance view. But there it just showed my "TOTAL DATA PULLED: 0 B" and restarted the container. Of course the container was not updated.
Â
Â
I then tried doing a docker pull in the CLI with the same URL as shown in the GUI and there it worked without a problem. As soon as I did the pull, I went back and retried the forced update, there of course, as excepted, it also pulled 0B and restarted the container with the new image since it now was present locally.
Â
Â
So I think the Problem may be that the URL has a port after the domain and so the Unraid updater thinks the port and beyond is already the tag and not part of the URL anymore. If that is really the problem it should be easily fixed by looking for ":" on the far right instead of the first.
Â
The Diagnostic file was generated right after trying to update the container in the GUI so maybe there is something there that can help.
Â
-
1
Recommended Comments
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.