You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using harbor proxy-cache to dockerhub. Pulling images like nginx with harbor proxy-cache is not a problem (HarborDomainName/proxy-cache/library/nginx), but when pulling images like vmware/harbor-log (HarborDomainName/proxy-cache/library/vmware/harbor-log), harbor can't read manifest and verify image existence.
The text was updated successfully, but these errors were encountered:
I think the image path for vmware/harbor-log should be HarborDomainName/proxy-cache/vmware/harbor-log
you are right, but this opens then the big problem. Most applications are written in the fashion they use registry in this format:
registryname/imagename, it means if imagename is nginx, it would throw error (HarborDomainName/proxy-cache/nginx), so there would be no fix to overwrite the default image URL settings with HarborDomainName/proxy-cache/ private registry string.
What can we help you?
I am using harbor proxy-cache to dockerhub. Pulling images like nginx with harbor proxy-cache is not a problem (HarborDomainName/proxy-cache/library/nginx), but when pulling images like vmware/harbor-log (HarborDomainName/proxy-cache/library/vmware/harbor-log), harbor can't read manifest and verify image existence.
The text was updated successfully, but these errors were encountered: