Conversation
…ll verification - Support registry-specific auth check via Docker config lookup - Add GHCR image pull access pre-verification using HTTP token exchange - Include target registry in all login log messages
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
1 participant
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.
Summary
check_docker_login()to accept a registry parameter and check Docker config for registry-specific auth entriesdocker compose pullTest plan
DSTACK_DOCKER_REGISTRY=docker.io(default Docker Hub)DSTACK_DOCKER_REGISTRY=ghcr.ioand valid GHCR credentialsDSTACK_DOCKER_REGISTRY=ghcr.ioand invalid/expired GHCR credentials to verify error path