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
there are annotations in the manifest, but having the same path
available for configuration specifc annotations seems logical as well.
Signed-off-by: Vincent Batts <[email protected]>
Copy file name to clipboardExpand all lines: config.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,6 +174,18 @@ Since the [configuration JSON](#image-json) that gets hashed references hashes o
174
174
This field is used to mark if the history item created a filesystem diff.
175
175
It is set to true if this history item doesn't correspond to an actual layer in the rootfs section (for example, a command like ENV which results in no change to the filesystem).
176
176
177
+
-**annotations***object*, OPTIONAL
178
+
179
+
contains arbitrary metadata for the container.
180
+
This information MAY be structured or unstructured.
181
+
Annotations MUST be a key-value map where both the key and value MUST be strings.
182
+
While the value MUST be present, it MAY be an empty string.
183
+
Keys MUST be unique within this map, and best practice is to namespace the keys.
184
+
Keys SHOULD be named using a reverse domain notation - e.g. `com.example.myKey`.
185
+
Keys using the `org.opencontainers` namespace are reserved and MUST NOT be used by subsequent specifications.
186
+
If there are no annotations then this property MAY either be absent or an empty map.
187
+
Implementations that are reading/processing this configuration file MUST NOT generate an error if they encounter an unknown annotation key.
188
+
177
189
Any extra fields in the Image JSON struct are considered implementation specific and should be ignored by any implementations which are unable to interpret them.
178
190
179
191
Whitespace is OPTIONAL and implementations MAY have compact JSON with no whitespace.
@@ -232,6 +244,11 @@ Here is an example image configuration JSON document:
0 commit comments