Copy to tar and back to repository doesn't always work #499
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
What steps did you take:
This is a little bit of an edge case where an image is shared between bundles which are nested bundles and only 1 of these bundles are collocated. This is more or less the diagram of the use case
To accomplish this we can do
1- Create one bundle with 1 image from repo1
2- Create a second bundle with the same image from repo1
3- Create a bundle on repo3 that points to both the previous bundles
4- imgpkg copy the bundle created in step 1 to the same repo as the bundle created in step 3
After this setup the issue can be triggered doing the following
1- Copy bundle from step 3 to tar
2- imgpkg copy the tar to a new repository
What happened:
imgpkg panics
What did you expect:
[A description of what was expected]
Anything else you would like to add:
The Root Cause problem is that when copying images from tar, imgpkg does not use the same path to generate an internal cache of the processed images that we are currently using in the copy from the repository to the repository. So when imgpkg is trying to create the ImagesLocation image and tries to see if the image will have all the needed images associated with the bundle it does not.
The bundle cache points to an OCI image in one repository but when we read the images from the tar the Ref present is from a different repository.
Environment:
imgpkg --version
): 0.36.0Docker HUB
): All/etc/os-release
): AllVote 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 work on this issue.
The text was updated successfully, but these errors were encountered: