media-types.md

Media Types

The following mediaType MIME types are used by the formats described here, and the resources they reference:

• application/vnd.oci.descriptor.v1+json: Content Descriptor
• application/vnd.oci.image.manifest.list.v1+json: Manifest list
• application/vnd.oci.image.manifest.v1+json: Image manifest format
• application/vnd.oci.image.serialization.rootfs.tar.gzip: "Layer", as a gzipped tar archive
• application/vnd.oci.image.serialization.config.v1+json: Container config JSON

Compatibility Matrix

The OCI Image Specification strives to be backwards and forwards compatible when possible. Breaking compatibility with existing systems creates a burden on users whether they be build systems, distribution systems, container engines, etc. This section shows where the OCI Image Specification is compatible with formats external to the OCI Image and different versions of this specification.

application/vnd.oci.image.manifest.list.v1+json

Similar/related schema

• application/vnd.docker.distribution.manifest.list.v2+json - mediaType is different

application/vnd.oci.image.manifest.v1+json

Similar/related schema

• application/vnd.docker.distribution.manifest.v2+json

application/vnd.oci.image.rootfs.tar.gzip

Interchangeable and fully compatible mime-types

• application/vnd.docker.image.rootfs.diff.tar.gzip

application/vnd.oci.image.serialization.config.v1+json

Similar/related schema

• application/vnd.docker.container.image.v1+json

Relations

The following figure shows how the above media types reference each other:

A reference is defined as the target content digest, as defined by the Registry V2 HTTP API Specificiation. The manifest list being a "fat manifest" references one or more image manifests per target platform. An image manifest references exactly one target configuration and possibly many layers.