-
Notifications
You must be signed in to change notification settings - Fork 211
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide alternate image registry to dockerhub #298
Comments
It is currently under investigation. Several considerations here:
Note that, ideally, we would need to also host the images we rely on in the same location. If a single dependency is still pulled from Docker hub, Quay or Github builds would also fail, being on the receiving end of the rate limiter. |
I'm not sure what Github is really limiting there, I've had no issues using GHCR with millions of pulls on open source projects. It's probably something you will never experience pain with. |
GHCR is part of GitHub Packages. Maybe this does not apply the way I think it does? |
I'm not entirely sure but if you look around you'll see a ton of OSS using GHCR for free and hosting their images without a problem. |
Given the recent dockerhub announcement of removing free team orgs, I'm wondering if the current org will be affected? And if so perhaps this could have a high priority? |
@Fusion sorry, not to poke too much but according to Docker you have 28 days from now to either pay Docker the $300/year cost or migrate the container elsewhere. |
Well, things got significantly worse. This now needs to be two conversations:
If the latter is not possible anymore, then the ramifications are manifold. |
Hello 馃憢馃徏
In order to combat dockerhub's imposed rate limits it would be great to host these images on ghcr (github container registry) or quay.io.
The text was updated successfully, but these errors were encountered: