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: image-layout.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ Given an image layout a tool can convert a given ref into a runnable OCI Image F
7
7
The image layout has two top level directories:
8
8
9
9
- "blobs" contains content-addressable blobs. A blob has no schema and should be considered opaque.
10
-
- "refs" contains descriptors pointing to an image manifest
10
+
- "refs" contains [descriptors][descriptors]. Commonly pointing to an image manifest.
11
+
11
12
12
13
It also contains a file that is used to identify the layout version:
13
14
@@ -45,7 +46,7 @@ The blobs directory MAY be missing referenced blobs, in which case the missing b
45
46
46
47
No semantic restriction is given for object names in the `refs` subdirectory.
47
48
Each object in the `refs` subdirectory MUST be of type `application/vnd.oci.descriptor.v1+json`.
48
-
In general the `mediatype` of this descriptor 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.
49
+
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.
49
50
50
51
This illustrates the expected contents of a given ref, the manifest list it points to and the blobs the manifest references.
0 commit comments