Explicitly use v2 scheme for v2 registry #56
Conversation
This file contains hidden or 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
Currently v2 registries uses v2+json header, otherwise one will get wrong digest returned. To ensure proper usage, explicitly set scheme v2.
lboclboc
approved these changes
Jan 29, 2020
djmattyg007
approved these changes
Aug 23, 2021
|
Hello. Since this package appears to be abandoned, I forked it and made several improvements. This includes dropping support for v1 registries, and introducing first-class support for v2 manifests (incluidng multi-arch manifests). Hopefully this makes your PR redundant! If you're feeling up to it, I'd really appreciate it if you could give my fork a go: |
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.
Currently v2 registries uses v2+json header, otherwise one will get
wrong digest returned. To ensure proper usage, explicitly set scheme v2.