Skip to content
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

Open
xaleeks opened this issue Aug 26, 2020 · 11 comments
Open

Proxy cache expanded support for additional registries #12885

xaleeks opened this issue Aug 26, 2020 · 11 comments
Assignees
Labels
area/proxy-cache kind/requirement New feature or idea on top of harbor

Comments

@xaleeks
Copy link
Contributor

xaleeks commented Aug 26, 2020

Support harbor acting as pull through cache for more registries beyond harbor and Dockerhub. continuation of #11658

@xaleeks xaleeks added kind/requirement New feature or idea on top of harbor area/proxy-cache candidate/2.2.0 labels Aug 26, 2020
@xaleeks xaleeks added this to Backlog in Harbor Project Board via automation Aug 26, 2020
@xaleeks xaleeks moved this from Backlog to 2.2 Product suggestions in Harbor Project Board Aug 26, 2020
@liangminhua
Copy link

please support docker registry

@ChristianCiach
Copy link

We have a local docker registry that is based on the image library/registry:2 from docker hub. If I lie to Harbor and configure this registry using "Provider: Harbor", the resulting proxy-cache seems to work just fine.

@xaleeks
Copy link
Contributor Author

xaleeks commented Nov 27, 2020

@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?

@ChristianCiach
Copy link

@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.

@xaleeks
Copy link
Contributor Author

xaleeks commented Nov 28, 2020

That sounds correct then, since Harbor is just running docker distribution on the inside.

@xaleeks
Copy link
Contributor Author

xaleeks commented Nov 28, 2020

I'm expecting GCR, Quay.io, ECR, ACR in that order of importance. Let me know if you disagree @steven-zou @stonezdj

@starkoff
Copy link

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.

@gw0
Copy link

gw0 commented Feb 8, 2021

Don't forget GitLab Container Registry, GitHub Container Registry, and already mentioned self-hosted Docker Registry 2.0.

@github-actions
Copy link

github-actions bot commented Jul 7, 2022

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.

@github-actions github-actions bot added the Stale label Jul 7, 2022
@olfway
Copy link

olfway commented Jul 7, 2022

up

@hinrichd
Copy link

It would be nice to have also support for GitLab Container Registry as proxy cache, too! THX

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/proxy-cache kind/requirement New feature or idea on top of harbor
Projects
Development

No branches or pull requests

9 participants