Fix retrieving manifest for single platform #23
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
lucacome
force-pushed
the
fix/single-manifest
branch
from
8c6e91c
to
47e2965
Compare
lucacome
force-pushed
the
fix/single-manifest
branch
from
47e2965
to
ed86949
Compare
Jakisuki85
approved these changes
Apr 2, 2023
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.
When the container is built for a single platform, the API responds with
application/vnd.docker.distribution.manifest.v1+jsonif it's not in the list of accepted formats.This fix adds
application/vnd.docker.distribution.manifest.v2+jsonto the accept list to read single platform manifests.It assumes that the platform is
linux/amd64since the manifest doesn't contain the info.Fixes #22