You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Content other than OCI container images MAY be packaged using the image manifest.
4
-
When this is done, the `config.mediaType` value MUST be set to a value specific to the artifact type or the [empty value](manifest.md#guidance-for-an-empty-descriptor).
5
-
Additional details and examples are provided in the [image manifest specification](manifest.md#guidelines-for-artifact-usage).
4
+
When this is done, the `config.mediaType` value should not be a known OCI image config [media type](media-types.md).
5
+
Historically, due to registry limitations, some tools have created non-OCI conformant artifacts using the `application/vnd.oci.image.config.v1+json` value for `config.mediaType` and values specific to the artifact in `layer[*].mediaType`.
6
+
Implementation details and examples are provided in the [image manifest specification](manifest.md#guidelines-for-artifact-usage).
3. For artifacts with a config blob, specify the `artifactType` to a common value for your artifact tooling, specify the `config` with the metadata for this artifact, and include the artifact in the `layers`.
_Implementers note:_ artifacts have historically been created without an `artifactType` field, and tooling to work with artifacts should fallback to the `config.mediaType` value.
0 commit comments