-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix compatibility with Docker 25+ #500
Conversation
Add support for OCI-compatible Docker images. Fixes #498
also fixes #452 |
Is it backwards compatible ? |
@Kerwood - I've confirmed this works with both the new format and is backwards compatible |
For those currently stuck (and don't want to build it themselves), I did build and publish it under my namespace (and it's multi-arch!). Image here - |
When is it going to be released? |
I'm shooting for today |
|
||
// 512 bytes ought to be enough (as that's the size of a TAR entry header), | ||
// but play it safe with 1024 bytes. This should also include very small layers | ||
// (unless they've also been gzipped, but Docker does not appear to do it) |
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.
I have a counter-example that's breaking this assumption, here's the layer from an image manifest that I've provided as a repro in #507
{
"schemaVersion": 2,
"mediaType": "application/vnd.oci.image.manifest.v1+json",
"config" { ... },
"layers": [
{ ... },
{ ... },
{
"mediaType": "application/vnd.oci.image.layer.v1.tar+gzip", // <- This layer is gzipped
"digest": "sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1",
"size": 32 // <- this layer is also very small
}
]
}
Add support for OCI-compatible Docker images.
Fixes #498