Replies: 2 comments 10 replies
-
I think we missed mentioning that the zstd-compressed image needs to be marked with annotation in the OCI index/manifest list: {
"mediaType": "application/vnd.oci.image.manifest.v1+json",
"digest": "sha256:bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
"size": 772,
"annotations": {
"io.github.containers.compression.zstd": "true"
},
"platform": {
"architecture": "amd64",
"os": "linux"
}
}, |
Beta Was this translation helpful? Give feedback.
10 replies
-
Will close this since Podman does prefer zstd:chunked images when the required annotations are added to the manifest |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
According to RHDan's forum post, the current container tools are smart enough to favour pulling zstd:chunked images from registries when in a manifest alongside gzipped images. Even if the gzipped image appears first.
Over at Universal Blue, we have started looking to push gzip and zstd:chunked alongside eachother, however are facing some strange behaviour when pulling or inspecting the images.
Our images:
ghcr.io/ublue-os/bluefin:40-testing
ghcr.io/ublue-os/bluefin@sha256:a78fe8009beeadb657bad6e76aa47e99b5b5945e618c3192b0ab4f77a06345ef
ghcr.io/ublue-os/bluefin@sha256:86d32d18a0eb7329293142bb0948b03e9a3896cde004f6faef0c60c3baac9375
When we target the manifest tag for during a
podman pull
, we receive the gzipped image where we would have expected the zstd image.When we target the manifest digest during a
skopeo inspect
, we receive information about the zstd:chunked image, which is expected.How can we ensure that users pull the chunked image when running with podman, while keeping compatibility with older tooling which does not support zstd:chunked?
We're not quite sure what we're missing, so any assistance would be greatly appreciated.
Thank you
Rob
Beta Was this translation helpful? Give feedback.
All reactions