How to force kaniko to build OCI images with oci manifests instead of docker manifests?

[titou10titou10]

Actual behavior I'm not sure if it is a bug or a question. I've read somewhrer that kaniko produces oci images by default but's its not the case for me

Currently when I use kaniko to bulld an image, the media type in the manifests is "application/vnd.docker.distribution.manifest.v2+json"

Q: how to force kaniko to produce images with manifests"application/vnd.oci.image.config.v1+json"?

When I use buildah for the same build, the image is of type"application/vnd.oci.image.config.v1+json"?

Expected behavior I want a way for the images produced by kaniko to have a media type of "application/vnd.oci.image.config.v1+json"

Additional Information

• kaniko v1.12.1

• build is run from tekton on OKD v4.13 (Fedora core OS 38.20230527.3.0)

• From the tekton task:

  • name: build image: gcr.io/kaniko-project/executor:v1.12.1 {...} args:
    • --dockerfile=$(params.DOCKERFILE)
    • --context=$(workspaces.code-git.path)/$(params.CONTEXT)
    • --destination=$(params.IMAGE_BASE):$(params.IMAGE_TAG)
    • --digest-file=$(results.IMAGE_DIGEST.path)

  Triage Notes for the Maintainers

  Description	Yes/No
  Please check if this a new feature you are proposing	- [ ]
  Please check if the build works in docker but not in kaniko	- [ ]
  Please check if this error is seen when you use --cache flag	- [ ]
  Please check if your dockerfile is a multistage dockerfile	- [ ]

[randlega]

Possibly related to: https://github.com/GoogleContainerTools/kaniko/issues/1836 ?