enforce OCI format for inner images when publishing tarballs or to local docker instances #47398
+9
−2
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
…cal docker instances
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
baronfel
added
Area-Containers
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.
Today it's possible to publish a multi-arch container manifest that is an OCI format, but contains inner images that are Docker format. This is an error - all formats (Docker or OCI) should be unified.
This PR determines if we are in a scenario in the outer-build where we are publishing an OCI manifest wrapper and forces the inner images to be OCI also.
Open Questions: