Add support for optional --buildkitd-config flag to buildx builder function #48
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.
What:
--buildkitd-configflag to thedocker buildx createfunctioncmdSetupBuildx(), passable withPLUGIN_BUILDER_CONFIGenvvarWhy:
Builders using the
docker-containerengine do not inherit some daemon config such as registry mirrors from the Docker daemon in their origin layer, and instead use a config file handed through a flag in theirdocker create buildxcommand - SourceThese changes allow users to optionally provide a
PLUGIN_BUILDER_CONFIGenvvar with a path to a Buildkit daemon config file, so registry mirrors can be added todocker-containerbuilders.Note:
--configis specified in configuring Buildkit registry mirrors but appears to be outdated, so I've added--buildkitd-configinstead as it's documented both here and in the flag list of the latest versiondocker create buildx --help