auth: add option to load docker config for specific repo/scope #3562
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
This was referenced Dec 11, 2025
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
tonistiigi
force-pushed
the
docker-config-scope-workaround
branch
from
07f5237 to
5adf89e
Compare
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.
Add the possibility to load an alternative Docker config (for registry auth) for a specific repository or scope. These configs can be put in
$DOCKER_CONFIG/buildx/config/registry[/repo/path][@scope[,..]].This should be considered workaround and support for this will NOT be extended to
docker login. Instead issue tracking support is in docker/cli#6695 and buildx would be updated if that issue progresses. We will add an option to use it in https://github.com/docker/login-action for advanced rate-limiting control that is needed there.