Handle OCI manifest and index with no mediaType #2824
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mpeddada1
reviewed
Oct 14, 2020
jib-core/src/main/java/com/google/cloud/tools/jib/registry/AbstractManifestPuller.java
Show resolved
Hide resolved
mpeddada1
approved these changes
Oct 14, 2020
jib-core/src/main/java/com/google/cloud/tools/jib/registry/AbstractManifestPuller.java
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #2819.
As explained in #2819, the Docker spec requires
mediaTypein a manifest or manifest list. OTOH, the OCI spec doesn't require it. Therefore, ifmediaTypeis not present (when schema 2), assume it's OCI.And
manifestsandconfigare required in an OCI manifest or index, respectively.