-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: support other Docker Registries like quay or docker hub #339
Comments
(I changed the title, if this feature is implemented then someone can still comment here and close it) |
I was really disappointed to find this limitation, as I run my own gitlab instance and would prefer my custom images to be hosted there. So, I did a little digging. The issue we have both run into appears to stem from this line. On gitlab, the token comes from I'm curious how the myriad of OCI tools handle this as pulling a container is universally transparent between them. |
Each registry returns the authentication URL in the response headers, which is what abroot should be using to get the proper url |
Github Container Registry is pretty unbearably slow, docker.io and quay.io are genuinely way faster, so i tried to make a mirror for vanilla, successfully (after 3 attempts) its at https://quay.io/repository/fluoritebyte/vanillaos-mirror-unofficial
the problem is that there is no sensible abroot config that i tried that worked for quay.io
the url that abroot forms to get the token seems to exclusively work with github, as it fails for docker hub.
and for the case of quay, it seems to accept 404 page as a valid response and continues with hasUpdate which then fails because quay (presumably) responds with an html/xml-like message, i do not know where to go from here
if anyone here that is knowledgeable about the insides of abroot and wants to help me, please do, im tired of waiting for updates to install at 100 kbit/s
The text was updated successfully, but these errors were encountered: