buildkitd: expose containerd Hyper-V isolation - #7067
Open
crazy-max wants to merge 1 commit into
Open
Conversation
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
buildkitd-hyperv-isolation
branch
from
August 24, 2026 10:04
42a5cc8 to
e5dcbc8
Compare
crazy-max
marked this pull request as ready for review
August 24, 2026 11:21
Member
Author
|
PTAL @rzlink |
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.
fixes #7062
This exposes the existing containerd executor support for Hyper-V isolation through standalone
buildkitdconfiguration. Windows users can now enable Hyper-V isolation for all build containers created by the containerd worker with--containerd-worker-hyperv-isolationor in TOML config.This covers standalone BuildKit usage where the executor option existed but couldn't be selected without patching the daemon. Docker Engine continues to use its own daemon default isolation wiring when it embeds BuildKit.