-
Notifications
You must be signed in to change notification settings - Fork 62
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
PlainImage should not fall back onto first image in the image index #142
Comments
When you are talking about the pull here, what do you see happening? |
this is a |
I tried the following:
Looks like that the first hint that this is not working 100% is in the output of the copy command. In a different topic, the output of the copy command doesn't look like it takes into account indexes, nevertheless, they are copied. |
images.NewImages is only used by the PlainImage. Maybe the best approach would be to remove this struct and directly in PlainImage check if the provided Image is an Image or an Index. Another point is the PlainImage.Pull should fail if the provided PlainImage is not an image, but it should not panic (current behavior) |
Currently imgpkg pull and copy end up pulling/copying first image of the image index. This is quite misleading because copy succeeds but actually does not copy image index (and other images in it). For pull it's surprising as well -- it's probably better to return an error to let the user know to give single image reference.
(i realized this when trying to
imgpkg copy -i nginx@sha256:... --to-repo dkalinin/private-repo
and not being able to pull that exact digest from private-repo)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.
The text was updated successfully, but these errors were encountered: