-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Proxy cache expanded support for additional registries #12885
Comments
please support docker registry |
We have a local docker registry that is based on the image |
@ChristianCiach I'm not sure I understand, what do you mean by 'based on the image from docker hub'. You are configuring a dockerhub endpoint as a harbor type endpoint? |
@xaleeks No, a "dockerhub endpoint" can only download images from docker hub (meaning docker.io). What I am trying to say is that we are using a private registry that is based on this image: https://hub.docker.com/_/registry To use harbor as a proxy cache for our private registry that is based on this image, I can configure a "harbor endpoint" in harbor, pointing it to our private registry, and it seems to work just fine. |
That sounds correct then, since Harbor is just running docker distribution on the inside. |
I'm expecting GCR, Quay.io, ECR, ACR in that order of importance. Let me know if you disagree @steven-zou @stonezdj |
Unfortunately. Not append in "New Registry Endpoint" Docker Hub. Message "Failed to ping endpoint." I can't get ping from hub.docker.com , but docker or docker compose works correctly. |
Don't forget GitLab Container Registry, GitHub Container Registry, and already mentioned self-hosted Docker Registry 2.0. |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
up |
It would be nice to have also support for GitLab Container Registry as proxy cache, too! THX |
Support harbor acting as pull through cache for more registries beyond harbor and Dockerhub. continuation of #11658
The text was updated successfully, but these errors were encountered: