ggcr: from scratch images created using obsolete application/vnd.docker.distribution.manifest.v2+json mediaType #2012
Labels
bug
Something isn't working
Comments
This was referenced Sep 19, 2024
I wouldn't go that far. |
|
@jonjohnsonjr as you have probably recognized in the PR, I have been mixing Docker image format v1 and v2. You are right, that Docker image v2 is not obsolete. The fact all the images I have checked in the Docker Hub Library are in OCI v1 mislead me. Nevertheless the issue that images built by Kaniko from scratch are created in Docker image v2, which gets rejected by OCI-only tools. I have to admit though, that Kaniko is not alone here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
empty.Imageis creating an empty container image with the obsolete mediaTypeapplication/vnd.docker.distribution.manifest.v2+jsonTo Reproduce
See related issue GoogleContainerTools/kaniko#3319
Expected behavior
Empty container images are created with current expected mediaType
application/vnd.oci.image.manifest.v1+json.Additional context
As a consequence of this bug, Kaniko images built from scratch get the obsolete mediaType
application/vnd.docker.distribution.manifest.v2+jsonand get rejected by OCI-only container registries (like ZOT).As mentioned above, the related Kaniko issue related issue GoogleContainerTools/kaniko#3319 gives much more context information.
I have been looking for the moment when Docker switch their default format from their legacy one to the current OCI one, but I could not find it. It is in any case not a very recent change.
The text was updated successfully, but these errors were encountered: