You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
crane export "image" argument is different from crane push.
I'm using rules_oci to generate images. I want to list the contents of the output of a oci_image target. The oci_image target is a directory that is accepted by crane push through the loadImage codepath:
I'm using crane export to try to get a tarball of the file system of the image. However, crane export doesn't process its image argument the same way. There is no call to ImageIndexFromPath etc.
As a result I don't have an easy way to inspect the filesystem contents of the image rules_oci produces using crane.
To Reproduce
TODO
Expected behavior
TODO
Additional context
Add any other context about the problem here.
$ dist/code5/external/oci_crane_linux_amd64/crane version
0.15.2
The text was updated successfully, but these errors were encountered:
Add --local-image flag to `crane export` to specify that the image argument is a
path, not a remote image.
If the flag is passed, the image may be either a tarball or a directory that's
loaded with ImageIndexFromPath.
Addresses google#1992.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.
Describe the bug
crane export
"image" argument is different fromcrane push
.I'm using rules_oci to generate images. I want to list the contents of the output of a
oci_image
target. Theoci_image
target is a directory that is accepted bycrane push
through theloadImage
codepath:go-containerregistry/cmd/crane/cmd/push.go
Lines 89 to 129 in c195f15
I'm using
crane export
to try to get a tarball of the file system of the image. However,crane export
doesn't process its image argument the same way. There is no call toImageIndexFromPath
etc.As a result I don't have an easy way to inspect the filesystem contents of the image rules_oci produces using crane.
To Reproduce
TODO
Expected behavior
TODO
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: