oci: Inline small content into manifest #1744
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for inlining content into the spin manifest. The immediate goal is to work around a problem with OCI implementations (discussed here: distribution/distribution#4029). Additionally, inlining small content should be an overall bandwith saver as each OCI layer has to be fetched in a separate HTTP request.
This PR starts inlining small (<=128 bytes) content, but continues to also upload layers for this content unless
SPIN_OCI_SKIP_INLINED_FILES
is set. Once downstream infrastructure supports content inlining we can make this the default.