fix: remove legacy registry API docker manifest create#190
Merged
Conversation
Signed-off-by: Shiva Kumar (SW-CLOUD) <shivaku@nvidia.com>
rajathagasthya
approved these changes
Jun 23, 2026
tariq1890
approved these changes
Jun 24, 2026
Contributor
Author
|
@rthallisey PTAL : refer : issue: 188 |
Collaborator
|
lgtm. Thanks |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
docker manifest create/pushuses the legacy registry API which pushes platform manifests individually, leaving them resolvable directly.nvcr.iothen resolves the tag to the amd64 platform manifest instead of the manifest list.docker buildx imagetools createuses the modern OCI API and creates a proper Docker manifest list where only the top-level digest is resolvable.