registryops: Fix --login-to arg behavior when using default registry #25
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
Until now when using the --login-to arg to login to a private container registry, if the specified registry is equal to the default one (in this case registry-1.docker.io), then the login credentials end up not being applied, resulting in a 'not authorized' error message. Signed-off-by: Lucas Akira Morishita <[email protected]>
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.
Until now when using the --login-to arg to login to a private container registry, if the specified registry is equal to the default one (in this case registry-1.docker.io), then the login credentials end up not being applied, resulting in a 'not authorized' error message.
Related-to: TCB-477
Signed-off-by: Lucas Akira Morishita [email protected]