From 034dbdfbccda7f5e3d3cae8887f8b4d0188d8d46 Mon Sep 17 00:00:00 2001 From: Monica Chao Date: Wed, 9 Apr 2025 07:37:03 -0500 Subject: [PATCH] docs: added note on populating builds tab when building windows container images (#22389) ## Description If a user switches to Windows containers and builds an image using the `docker build` command as it (using the legacy builder), the Builds tab is not populated. This is because the build history is provided by Buildkit. To populate the Builds tab, the customer must either set `DOCKER_BUILDKIT=1` or use the `buildx build` command. Current documentation does not mention this and a support ticket was raised. ## Related issues or tickets - SEG-1116 (Slack thread linked in ticket for context) ## Reviews - [X] Technical review @karman-docker - [X] Editorial review - [ ] Product review --------- Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> --- content/manuals/desktop/use-desktop/builds.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/manuals/desktop/use-desktop/builds.md b/content/manuals/desktop/use-desktop/builds.md index 71c32fe35e..c31b1e6114 100644 --- a/content/manuals/desktop/use-desktop/builds.md +++ b/content/manuals/desktop/use-desktop/builds.md @@ -14,6 +14,12 @@ If you're connected to a cloud builder through [Docker Build Cloud](../../build- the Builds view also lists any active or completed cloud builds by other team members 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 + ## Show build list Open the **Builds** view from the Docker Dashboard to access: