-
Notifications
You must be signed in to change notification settings - Fork 201
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
[WIP] Add multi manifest oci-archive support #921
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: umohnani8 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a very quick skim. It seems the commit is reverting some previous ones.
5b1833d
to
c0f3141
Compare
c811431
to
1331f03
Compare
d4a38e5
to
f9d3e66
Compare
985c8a5
to
8779bc6
Compare
71a2345
to
219ab4e
Compare
if err != nil { | ||
return nil, err | ||
} | ||
return r.copyFromOCIArchiveReader(ctx, reader, options) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If readerRef
points at specific image, this seems to completely lose that choice.
Cc: @vrothberg . I thought the distinction is that podman pull oci-archive:…
always pulls exactly the one image that c/image uses under that reference, while podman load
can possibly pull all images from an archive.
(Compare also the discussion about NewReaderForReference
/ LoadManifestDescriptor
in the c/image PR.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cc: @vrothberg . I thought the distinction is that podman pull oci-archive:… always pulls exactly the one image that c/image uses under that reference, while podman load can possibly pull all images from an archive.
Yes, podman pull
expects one image. You can check out the behavior via podman pull docker-archive:libimage/testdata/docker-two-images.tar.xz
Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>
302dfba
to
c9cd8ba
Compare
} | ||
defer func() { | ||
if err := reader.Close(); err != nil { | ||
logrus.Errorf(err.Error()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.Error()
is not a format string; this should be something like logrus.Errorf("%s", err.Error())
@umohnani8: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>
Can we close this one due to lack of activity? |
Pulling in containers/image#1381 and adding it to the load and save logic here.