microsoft/Windows-Containers

Can build with bulidctl but nerdctl build cannot

tgckpg opened this issue · 3 comments

I am trying to build windows container images.

nerdctl output

$ nerdctl build
time="2024-04-11T14:03:35+09:00" level=fatal msg="`buildctl` needs to be installed and `buildkitd` needs to be running, see https://github.com/moby/buildkit: only linux and freebsd are supported"

$ nerdctl version
time="2024-04-11T14:04:58+09:00" level=warning msg="unable to determine runc version: exec: \"runc\": executable file not found in %PATH%"
Client:
 Version:       v1.7.5
 OS/Arch:       windows/amd64
 Git commit:    cffed372371dcbea3dc9a646ce5a913fc1c09513
 buildctl:
  Version:      v0.13.1
  GitCommit:    2ae42e0c0c793d7d66b7a23424af6fd6c2f9c8f3

Server:
 containerd:
  Version:      v1.7.15
  GitCommit:    926c9586fe4a6236699318391cd44976a98e31f1
 runc:
  Version:

buildctl output

$ buildctl debug info
BuildKit: github.com/moby/buildkit v0.13.1 2ae42e0c0c793d7d66b7a23424af6fd6c2f9c8f3

$ buildctl build --frontend dockerfile.v0 --local dockerfile=.
[+] Building 150.5s (8/14)
 => [internal] load build definition from Dockerfile                                                                                                        0.1s
 => => transferring dockerfile: 3.06kB                                                                                                                      0.0s
 => [internal] load metadata for mcr.microsoft.com/windows/servercore:1903-amd64                                                                            0.8s
 => [internal] load metadata for mcr.microsoft.com/powershell:nanoserver-1903                                                                               0.8s
 => ERROR [internal] load .dockerignore                                                                                                                     0.1s
 => => transferring context:                                                                                                                                0.0s
 => [stage-1 1/8] FROM mcr.microsoft.com/powershell:nanoserver-1903@sha256:81f6b1c06d3e064f1cc29415e87919fa9136564a958b7190ed1d5a17be7b9cb3               149.3s
 => => resolve mcr.microsoft.com/powershell:nanoserver-1903@sha256:81f6b1c06d3e064f1cc29415e87919fa9136564a958b7190ed1d5a17be7b9cb3                         0.1s
 => => sha256:02a46850464f896128d38032429af01ed881c9561496b85a7dcf75894d1cfd3f 101.72MB / 101.72MB                                                         51.0s
 => => sha256:da83f3e327d6be0778a2e9cb3bdbcd4381d91d53be27a9d83e7a02d713898ab6 69.12kB / 69.12kB                                                            0.9s
 => => sha256:b251ece4f860cf57423dd1455d77586f293f469389d4e8f22eda21f3f3865674 921B / 921B                                                                  1.0s
 => => sha256:de401d0ad50a73809f52f1b2cdd08372d48affaed3cdc2d9c82fd93fdb86935d 0B / 822B                                                                  146.4s
 => => sha256:302b7cf33b3a2bd3c958c33a0bb0221099c7abebd46bd685a171899210be5180 102.87MB / 102.87MB                                                         59.5s
 => => extracting sha256:302b7cf33b3a2bd3c958c33a0bb0221099c7abebd46bd685a171899210be5180                                                                  72.4s
 => => extracting sha256:de401d0ad50a73809f52f1b2cdd08372d48affaed3cdc2d9c82fd93fdb86935d                                                                   0.3s
 => => extracting sha256:b251ece4f860cf57423dd1455d77586f293f469389d4e8f22eda21f3f3865674                                                                   0.3s
 => => extracting sha256:da83f3e327d6be0778a2e9cb3bdbcd4381d91d53be27a9d83e7a02d713898ab6                                                                   5.5s
 => => extracting sha256:128bd25e4a5fd56d89d1d3519ab5299fad89e0fa26b42a19bbcacf3ffc63a75a                                                                   0.3s
 => => extracting sha256:02a46850464f896128d38032429af01ed881c9561496b85a7dcf75894d1cfd3f                                                                   7.0s
 => [dlls 1/2] FROM mcr.microsoft.com/windows/servercore:1903-amd64@sha256:2a43600b6e91dd42ed9c692743898f4480e400e66a3b1bd0a9fc01876fd330f0               149.4s
 => => resolve mcr.microsoft.com/windows/servercore:1903-amd64@sha256:2a43600b6e91dd42ed9c692743898f4480e400e66a3b1bd0a9fc01876fd330f0                      0.1s
 => => sha256:4371cb55e8ebd2e23b5b68f3e3f2015dda376eb8a6353f7f7da1fdee9c038d26 403.70MB / 814.67MB                                                        148.9s
 => => sha256:5b663e3b9104ae6bf9135c0beb5291952314d59565b1be257a362a53b219b889 404.75MB / 1.53GB                                                          148.8s

@tgckpg Hi, were you able to build with nerdctl?

@tgckpg Hi, were you able to build with nerdctl?

Sorry I posted on the wrong repo. But yes at the end I was able to build it with the beta version of nerdctl. The current version (v1.7.5) won't work.

No problem, I was just curious. Thanks!