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

Commit

Permalink
PR feedback for layer processing
Browse files Browse the repository at this point in the history 
Signed-off-by: Steve Lasker <stevelasker@hotmail.com>
  • Loading branch information
Steve Lasker committed Apr 7, 2020
1 parent 876538d commit 3ceb791
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion spec.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ Defining artifact layers involves:

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.

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.
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.

### Layer Content Format

Expand Down

0 comments on commit 3ceb791

Please sign in to comment.