-
Notifications
You must be signed in to change notification settings - Fork 27
Use diffids - fix pulling from containers-storage:
#153
Comments
Alternatively the proxy could expose LayerInfosForCopy, to be closer to what the c/image/copy code does and assumes. (Admittedly LayerInfosForCopy is a wart that shouldn’t exist in the first place… between exposing that and hard-coding |
What we really want is ostreedev/ostree-rs-ext#153 to support pushing/pulling directly from `containers-storage`, but in the short term this should improve CI times.
Just noting that https://github.com/RishabhSaini is planning to look at this |
I'd second the suggestion to expose and use A v2s1 image isn't going to have any DiffID values in the OCI-format config blob that is synthesized for it (observe:
|
|
Today we're using https://github.com/containers/containers-image-proxy-rs which is a Rust binding to https://github.com/containers/skopeo/blob/main/cmd/skopeo/proxy.go which is an IPC interface to containers/image.
In our usage of this, we fetch by blob right now. Operating system upgrades for example work fine fetching from a remote registry (e.g.
quay.io/fedora/fedora-coreos:stable
) - we stream and uncompress the blobs, writing to ostree.However, it doesn't work to fetch by blob ID (compressed tar) from
containers-storage
because it only has the uncompressed version. We need to fetch via diffid.We need containers/skopeo#1495 to fetch the config blob, then the pull code should use it.
The text was updated successfully, but these errors were encountered: