feat: unify Docker registry handling via oras and adjust image processing order#71
Open
k1shk1n wants to merge 18 commits intoNetcracker:mainfrom
Open
feat: unify Docker registry handling via oras and adjust image processing order#71k1shk1n wants to merge 18 commits intoNetcracker:mainfrom
k1shk1n wants to merge 18 commits intoNetcracker:mainfrom
Conversation
…; tests; up oras version
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
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.
Unify docker registries handling by using oras: support OCI Distribution Specs and Docker Registry HTTP API v2 (with Registry Authentication) and more native usage similar to docker cli
TODO:
Breaking changes:
--registry-typecli parameter fromdownload,installanduninstallcli commands. ps may be we need to obtain this parameter (but not use it) so as not to break the processes of users who have hardcoded this parameter when using the cli in their orchestration (right now, any unknown parameter = error)--registry-typecli parametertest registries: