setup proxy cache to Google Artifact registry is failing · goharbor/harbor#20682

(13 comments) (1 reaction) (1 assignee)Go (28,490 stars) (5,235 forks)batch import

area/proxy-cachehelp wantedkind/requirement

説明

I have installed harbor and setup ingress and added a proxy registry with Google GCR provider but with Artifact registry as the Endpoint URL(https://us-docker.pkg.dev/<GCP_PROJECT>).

But when i am trying to pull from the harbor endpoint, it is giving the below error. Error response from daemon: unknown: repository proxy-cache/prod-docker-us/hello-world not found

Docker login works and i am using the command in the format as below: docker pull <HARBOR_ENDPOINT>/<HARBOR_PROJECT_NAME>/<GAR_REPO_NAME>/hello-world:latest

And i was able to pull the image from GAR successfully using Google Artifact Registry endpoint.

After checking the harbor-core pod logs, i could see the below logs: 2024-07-01T19:43:19Z [ERROR] [/server/middleware/repoproxy/proxy.go:121]: failed to proxy manifest, fallback to local, request uri: /v2/proxy-cache/hello-world/manifests/latest, error: http status code: 405, body:

コントリビューターガイド

技術スタック: godockergcp
領域: backendinfrastructurecloud
Issue 種別: bug
難度: 3
推定時間: 1-2 days
活動状況: blocked
明確さ: clear
前提条件: Docker knowledgeHarbor proxy cache setupGCP Artifact Registry
初心者向け度: 30
調査方針: Start by examining the proxy.go file in the server/middleware/repoproxy directory, specifically around line 121 where the 405 error is logged. Review the logic for handling proxy requests to Google Artifact Registry and compare with the expected behavior for GCR. Check the comments in the issue for any additional diagnostic steps or proposed solutions. Ensure that the endpoint URL format matches what Harbor expects for a proxy cache.