Relocating bundle to Google Artifact Registry using --repo-based-tags
fails
#582
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
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
What steps did you take:
where
SRC_REPO
is hosted on harbor registry (at least I think so) and is a bundle referencing multiple other bundles & imagesTAG
is a specific tag, like1.7.0-build.75
What happened:
The relocation failed on the very same artifact, consistently, when using
--repo-based-tags
. After further testing we've found that relocating the bundle generally works, only when using the--repo-based-tags
flag we see this issue.It seems like the problem is the leading
.
for.dev-pkg-apiextensions-storageversion-cmd-migrate-sha256-752dc730211b9daabec7b9e978e4cc22fd217bf49a8896e67fd73e01a4ba2c9e.imgpkg
.I am not sure if this is a problem with:
Running with
--debug
showed some more info:What did you expect:
The bundle to be relocated, including all its referenced artifacts.
Anything else you would like to add:
--repo-based-tags
workseurope-docker.pkg.dev/...
andus-docker.pkg.dev/...
imgpkg copy
slightly different, but all showed the very same error--to-tar
) and upload from that (--tar
&--to-repo
)--concurrency
, down to1
.
thoEnvironment:
imgpkg --version
): 0.38.0Docker HUB
): Google Artifact Registry/etc/os-release
): Linux 6.2.0 / UbuntuVote 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.
The text was updated successfully, but these errors were encountered: