Clarify legacy builder note for Windows container builds#24587
Merged
dvdksn merged 2 commits intodocker:mainfrom Mar 31, 2026
Merged
Clarify legacy builder note for Windows container builds#24587dvdksn merged 2 commits intodocker:mainfrom
dvdksn merged 2 commits intodocker:mainfrom
Conversation
Rewrite the note to use active voice and explain the workaround more clearly: the docker build command uses a legacy builder, and here is how to switch to BuildKit. Fixes docker#24453
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
dvdksn
reviewed
Mar 31, 2026
dvdksn
approved these changes
Mar 31, 2026
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
2 participants
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.
Description
The note about Windows container builds uses passive voice ("the legacy builder is used") which makes the behavior unclear. Readers can't tell if this is expected behavior or a temporary limitation.
Rewritten in active voice to make the cause and workaround clear: the
docker buildcommand uses a legacy builder, and here is how to switch to BuildKit to see builds in the Builds view.Fixes #24453