Skip to content
This repository was archived by the owner on Jul 18, 2023. It is now read-only.

Commit 19d53e8

Browse files
author
Steve Lasker
committed
PR feedback for layer processing
Signed-off-by: Steve Lasker <stevelasker@hotmail.com>
2 parents d7df3dc + 5a2a5e1 commit 19d53e8

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

spec.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Defining artifact layers involves:
122122

123123
As an example, [OCI Images][image-layer] are represented through an ordinal collection of tar archives. Each blob represents a layer. Each layer overlays the previous layer.
124124

125-
Some artifacts may be represented as a single file, such as config artifact representing a deployment specification. While other artifacts may include a config object, and a collection of binaries compressed as yet another layer. By separating the layers, the artifact author can benefit from layer de-duplication and concurrent downloading of each layer using various distribution-spec clients.
125+
Some artifacts may be represented as a single file, such as config artifact representing a deployment specification. While other artifacts may include a config object, and a collection of binaries compressed as yet another layer. By separating the layers, the artifact author can benefit from layer de-duplication and concurrent downloading of each layer using various distribution-spec clients. How an artifact client processes layers, merging them with overlay, or extracting them to different locations or hosts is up to the artifact authors.
126126

127127
### Layer Content Format
128128

0 commit comments

Comments
 (0)