From b64e6dbb774e1d0005a268172c7f3c13b6d6d869 Mon Sep 17 00:00:00 2001 From: Anthony Nandaa Date: Tue, 10 Jun 2025 19:50:24 +0300 Subject: [PATCH] buildkit: windows: add a note for managed containerd process If you run two instanced of `containerd` one being used by the standalone `buildkitd.exe` and another one being managed by `dockerd.exe`, you end up with some conflicts and errors like: ``` hcsshim::ImportLayer failed in Win32: Cannot create a file when that file already exists. (0xb7) ``` This fix adds a note to guide the user to use only one instance of `containerd` instead, if for this purpose. --- content/manuals/build/buildkit/_index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/manuals/build/buildkit/_index.md b/content/manuals/build/buildkit/_index.md index 89d75f2ad539..35afb1ee6ad9 100644 --- a/content/manuals/build/buildkit/_index.md +++ b/content/manuals/build/buildkit/_index.md @@ -154,7 +154,7 @@ see [GitHub issues](https://github.com/moby/buildkit/issues?q=is%3Aissue%20state 4. Download and extract the latest BuildKit release. ```powershell - $version = "v0.13.1" # specify the release version, v0.13+ + $version = "v0.22.0" # specify the release version, v0.13+ $arch = "amd64" # arm64 binary available too curl.exe -LO https://github.com/moby/buildkit/releases/download/$version/buildkit-$version.windows-$arch.tar.gz # there could be another `.\bin` directory from containerd instructions @@ -184,6 +184,9 @@ see [GitHub issues](https://github.com/moby/buildkit/issues?q=is%3Aissue%20state ```console > buildkitd.exe ``` + > [!NOTE] + > If you are running a _dockerd-managed_ `containerd` process, use that instead, by supplying the address: + > `buildkitd.exe --containerd-worker-addr "npipe:////./pipe/docker-containerd"` 7. In another terminal with administrator privileges, create a remote builder that uses the local BuildKit daemon.