-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support pulling zstd-compressed base layers #3714
Comments
Thank you; we'll keep the feature request open to gauge community interest in the new format. |
The stacktrace is a bit clearer with jib-core 0.21.0: Stacktrace
Looking at the moby implementation, they look at the magic bytes of the input stream to detect the type of compression (Bzip2, Gzip, Xz, Zstd). I'm going to open a PR so you can review the feasibility / design / impacts. |
Thank you for your contribution! |
Environment:
Description of the issue:
Jib should support pulling image layers that use the new
application/vnd.oci.image.layer.v1.tar+zstd
(cf https://github.com/opencontainers/image-spec/blob/main/media-types.md).Currelty only
application/vnd.oci.image.layer.v1.tar+gzip
is supportedWhen trying to build from an image like https://hub.docker.com/r/gscrivano/zstd-chunked, Jib will fail with:
Additional information:
More info on zstd-chunked compression: https://www.redhat.com/sysadmin/faster-container-image-pulls
PR for zstd support in docker: moby/moby#41759. Note: the support is only in Beta version, with 20.10.16
docker pull gscrivano/zstd-chunked:fedora
fails withError processing tar file(exit status 1): archive/tar: invalid tar header
The ability to create zstd-compressed layers with Jib itself is likely a separate feature, in a first step Jib should not crash when pulling such layers.
The text was updated successfully, but these errors were encountered: