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
Copy file name to clipboardexpand all lines: considerations.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Extensibility
2
2
3
-
Implementations that are reading/processing [manifests](manifest.md) or [manifest lists](manifest-list.md) MUST NOT generate an error if they encounter an unknown property.
3
+
Implementations that are reading/processing [manifests](manifest.md) or [image index](image-index.md) MUST NOT generate an error if they encounter an unknown property.
Copy file name to clipboardexpand all lines: image-layout.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This layout MAY be used in a variety of different transport mechanisms: archive
5
5
6
6
Given an image layout and a ref, a tool can create an [OCI Runtime Specification bundle](https://github.com/opencontainers/runtime-spec/blob/v1.0.0-rc2/bundle.md) by:
7
7
8
-
* Following the ref to find a [manifest](manifest.md#image-manifest), possibly via a [manifest list](manifest-list.md#manifest-list)
8
+
* Following the ref to find a [manifest](manifest.md#image-manifest), possibly via a [image index](image-index.md#manifest-list)
9
9
*[Applying the filesystem layers](layer.md#applying) in the specified order
10
10
* Converting the [image configuration](config.md) into an [OCI Runtime Specification `config.json`](https://github.com/opencontainers/runtime-spec/blob/v1.0.0-rc2/config.md)
11
11
@@ -16,7 +16,7 @@ The image layout MUST contain two top level directories:
16
16
-`blobs` contains content-addressable blobs.
17
17
A blob has no schema and should be considered opaque.
18
18
-`refs` contains [descriptors][descriptors].
19
-
Commonly pointing to an [image manifest](manifest.md#image-manifest) or an [image manifest list](manifest-list.md#oci-image-manifest-list-specification).
19
+
Commonly pointing to an [image manifest](manifest.md#image-manifest) or an [image index](image-index.md#oci-image-manifest-list-specification).
20
20
21
21
Both `blobs` and `refs` MAY be empty.
22
22
@@ -59,7 +59,7 @@ Object names in the `refs` subdirectories MUST NOT include characters outside of
59
59
60
60
No semantic restriction is given for object names in the `refs` subdirectory.
61
61
Each object in the `refs` subdirectory MUST be of type `application/vnd.oci.descriptor.v1+json`.
62
-
In general the `mediaType` of this [descriptor][descriptors] object will be either `application/vnd.oci.image.manifest.list.v1+json` or `application/vnd.oci.image.manifest.v1+json` although future versions of the spec MAY use a different mediatype.
62
+
In general the `mediaType` of this [descriptor][descriptors] object will be either `application/vnd.oci.image.index.v1+json` or `application/vnd.oci.image.manifest.v1+json` although future versions of the spec MAY use a different mediatype.
63
63
64
64
**Implementor's Note:**
65
65
A common use case of refs is representing "tags" for a container image.
@@ -69,14 +69,14 @@ Those tags will often be represented in an image-layout repository with matching
69
69
70
70
### Example Ref
71
71
72
-
This is an example `v1.0`ref with a manifest-list descriptor:
72
+
This is an example ref named `v1.0` with a image-index descriptor:
Copy file name to clipboardexpand all lines: manifest.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,15 @@
3
3
There are three main goals of the Image Manifest Specification.
4
4
The first goal is content-addressable images, by supporting an image model where the image's configuration can be hashed to generate a unique ID for the image and its components.
5
5
The second goal is to allow multi-architecture images, through a "fat manifest" which references image manifests for platform-specific versions of an image.
6
-
In OCI, this is codified in a [Manifest List](manifest-list.md).
6
+
In OCI, this is codified in a [Image Index](image-index.md).
7
7
The third goal is to be translatable to the [OCI Runtime Specification](https://github.com/opencontainers/runtime-spec).
8
8
9
9
This section defines the `application/vnd.oci.image.manifest.v1+json`[media type](media-types.md).
10
10
For the media type(s) that this is compatible with see the [matrix](media-types.md#compatibility-matrix).
11
11
12
12
# Image Manifest
13
13
14
-
Unlike the [Manifest List](manifest-list.md), which contains information about a set of images that can span a variety of architectures and operating systems, an image manifest provides a configuration and set of layers for a single container image for a specific architecture and operating system.
14
+
Unlike the [Image Index](image-index.md), which contains information about a set of images that can span a variety of architectures and operating systems, an image manifest provides a configuration and set of layers for a single container image for a specific architecture and operating system.
-`application/vnd.oci.image.layer.v1.tar`: ["Layer", as a tar archive](layer.md)
@@ -31,7 +31,7 @@ The OCI Image Specification strives to be backwards and forwards compatible when
31
31
Breaking compatibility with existing systems creates a burden on users whether they are build systems, distribution systems, container engines, etc.
32
32
This section shows where the OCI Image Specification is compatible with formats external to the OCI Image and different versions of this specification.
0 commit comments