ctr pull images err archive/tar: invalid tar header: unknown about containerd HOT 5 CLOSED

On my end it looks like this was an issue with bazel docker rules, unrelated to containerd/docker -- https://github.com/bazelbuild/rules_docker/blob/master/container/go/pkg/compat/image.go#L175-L180

It looks like in 25.0 docker started outputting OCI compliant tarballs, and it seems like by properly marking uncompressed layers as application/vnd.oci.image.layer.v1.tar, revealed a bug where the bazel rule always assumes that the media type is compressed.

from containerd.

Seeing a similar problem, looks a lot like #3326, except we're using docker instead of buildah -- after upgrading docker we're seeing blobs that were previously marked as application/vnd.docker.image.rootfs.diff.tar.gzip (using docker 24.0.5) as application/vnd.oci.image.layer.v1.tar (using docker 25.0.3) -- feels like it should be application/vnd.oci.image.layer.v1.tar+gzip instead.

It looks like the docker pull is automatically detecting that the blob is gzipped, while containerd doesn't -- technically containerd's behavior is correct according to the spec ofc.

from containerd.

Mostly grasping at straws, might be related to this string of commits, since seems like the main spots where application/vnd.oci.image.layer.v1.tar (i.e. ocispec.MediaTypeImageLayer) has been used thats new between 24.0 and 25.0

• moby/moby@2c45df2
• moby/moby@9f50e06
• moby/moby@c58acf0

from containerd.

Would either of you be able to make or share a public image that reproduces the problem? Or steps to build an image that reproduces the problem? 👀

from containerd.

@tianon @ckw017 My solution to this problem was to rebuild the image, but it did not solve the underlying problem

from containerd.