-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
helm: harbor as generic registry mirror #16053
Comments
Harbor 2.0+ doesn't support registry mirror. If you want this feature, suggest deploying standalone distribution support the registry mirror. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Will this feature be supported in the future? |
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. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
Leaving this here for whoever is also mislead by this issue. https://goharbor.io/docs/1.10/administration/configuring-replication/ |
Hello,
I am trying to replace the docker registry mirror with harbor, without reconfiguring everything that use it on my network.
I have deployed harbor v2.4.0 using helm (using ingress), and tried to configure it as a registry-mirror in my docker/daemon.json. When I docker pull, image seams to be pulled from docker registry, not harbor.
It seams there is a way to have harbor as registry mirror : https://github.com/goharbor/harbor/blob/master/contrib/Configure_mirror.md
Looks like #8082 already addressed this case, but I did not managed to make it work.
Is there a full complete working doc I can follow and test ? Or where should I search for diagnostics ?
Edit : found in ingress logs that harbor returns 401 for registry-proxy requests
The text was updated successfully, but these errors were encountered: