Clarify legacy builder note for Windows container builds (#24587)

lacatoire · web-flow · commit 658a21f6c4db · 2026-03-31T13:19:21.000+02:00
## 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 build` command uses a legacy builder, and here is how to switch to BuildKit to see builds in the Builds view. Fixes #24453
diff --git a/content/manuals/desktop/use-desktop/builds.md b/content/manuals/desktop/use-desktop/builds.md
@@ -16,9 +16,7 @@ connected to the same cloud builder.
 
 > [!NOTE]
 >
-> When building Windows container images using the `docker build` command, the legacy builder is used which does not populate the **Builds** view. To switch to using BuildKit, you can either:
-> - Set `DOCKER_BUILDKIT=1` in the build command, such as `DOCKER_BUILDKIT=1 docker build .` or
-> - Use the `docker buildx build` command
+> Windows container image builds use the legacy builder and do not appear in the **Builds** view. Only BuildKit-powered builds are shown here.
 
 ## Show build list
 

Original file line number	Diff line number	Diff line change
`@@ -16,9 +16,7 @@ connected to the same cloud builder.`
`16`	`16`
`17`	`17`	`> [!NOTE]`
`18`	`18`	`>`
`19`		-> When building Windows container images using the `docker build` command, the legacy builder is used which does not populate the Builds view. To switch to using BuildKit, you can either:
`20`		-> - Set `DOCKER_BUILDKIT=1` in the build command, such as `DOCKER_BUILDKIT=1 docker build .` or
`21`		-> - Use the `docker buildx build` command
	`19`	`+> Windows container image builds use the legacy builder and do not appear in the Builds view. Only BuildKit-powered builds are shown here.`
`22`	`20`
`23`	`21`	`## Show build list`
`24`	`22`