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

imgpkg copy between harbor projects fails with auth error #495

Open
cjnosal opened this issue Mar 8, 2023 · 3 comments
Open

imgpkg copy between harbor projects fails with auth error #495

cjnosal opened this issue Mar 8, 2023 · 3 comments
Labels
bug This issue describes a defect or unexpected behavior carvel accepted This issue should be considered for future work and that the triage process has been completed

Comments

@cjnosal
Copy link

cjnosal commented Mar 8, 2023

What steps did you take:
1 docker login my-harbor.registry # creds have rw access to both project1 and project2
2.a imgpkg copy -b my-harbor.registry/project1/repo --to-repo my-harbor.registry/project2/repo
or
2.b

imgpkg copy -b my-harbor.registry/project1/repo --to-tar mytar
imgpkg copy --tar mytar --to-repo my-harbor.registry/project2/repo

What happened:
Failed with unauthorized error.
/v2/project2/repo/blobs/uploads/?from=project1%2frepo&mount=sha256:...&origin=my-harbor.registry

What did you expect:

  1. imgpkg copy to succeed by falling back to less efficient copy if the optimized mount approach fails
  2. imgpkg copy --from-tar should not require access to the location the tar originated from

Anything else you would like to add:
Harbor projects are a permissions boundary which might be blocking the cross-project mount

Environment:

  • imgpkg version (use imgpkg --version): v0.35.0
  • Docker registry used (e.g. Docker HUB): Harbor Version v2.3.3-a0a9ed8a
  • OS (e.g. from /etc/os-release): ubuntu 20.04.5

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@cjnosal cjnosal added bug This issue describes a defect or unexpected behavior carvel triage This issue has not yet been reviewed for validity labels Mar 8, 2023
@joaopapereira joaopapereira added carvel accepted This issue should be considered for future work and that the triage process has been completed and removed carvel triage This issue has not yet been reviewed for validity labels Apr 4, 2023
@joaopapereira
Copy link
Member

This looks like a behavior that needs to be changed at ggcr level.

Because if this fails we will return here with an error and mounted == false. Which means that in here we will return an error

@joaopapereira
Copy link
Member

Waiting on feedback from google/go-containerregistry#1609

@Mai-Khattab
Copy link

Hello,

Was that fixed at any release? I am facing the same using imgpkg version 0.43.0 when copying bundles from (projects.registry.vmware.com) to Harbor v2.6.4.

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes a defect or unexpected behavior carvel accepted This issue should be considered for future work and that the triage process has been completed
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

3 participants