Can't find runtime "io.containerd.spin.v1"/"io.containerd.wasmtime.v1" in Docker 4.18.0

rts-gordon commented 1 year ago

[x] I have tried with the latest version of Docker Desktop
[x] I have tried disabling enabled experimental features
[ ] I have uploaded Diagnostics

Actual behavior

I try test some Wasm programs from this Blog "Announcing Docker+Wasm Technical Preview 2" in Docker 4.18.0.

1, when I execute "docker run --rm --runtime=io.containerd.wasmedge.v1 --platform=wasi/wasm secondstate/rust-example-hello:latest", that is OK.

2, when I execute "docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm secondstate/rust-example-hello:latest", there are errors:

docker: Error response from daemon: failed to create task for container: failed to start shim: failed to resolve runtime path: runtime "io.containerd.wasmtime.v1" binary not installed "containerd-shim-wasmtime-v1": file does not exist: unknown.

3, I cloned this repo and build the docker image, when I execute "docker run --runtime=io.containerd.spin.v1 -p 3000:80 my-cms", there are errors:

docker: Error response from daemon: failed to create task for container: failed to start shim: failed to resolve runtime path: runtime "io.containerd.spin.v1" binary not installed "containerd-shim-spin-v1": file does not exist: unknown.

Expected behavior

Docker runtime "io.containerd.wasmtime.v1/io.containerd.spin.v1" can be installed and those Wasm programs can run in Docker. But I didn't find how to install or enable those special runtimes, thanks for any help.

Information

Windows Version: Windows 10
Docker Desktop Version: 4.18.0
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: Windows 10 running on a laptop

Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check`

Output

PS C:\Program Files\Docker\Docker\resources> ./com.docker.diagnose.exe check [2023-04-18T23:35:35.260116400Z][com.docker.diagnose.exe][I] set path configuration to OnHost Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [FAIL] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:36.648306600Z][com.docker.diagnose.exe][I] ipc.NewClient: cbf5fad9-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-04-18T23:35:36.648920300Z][com.docker.diagnose.exe][I] (c92cbf8e) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /hyp erv/bootloader [2023-04-18T23:35:36.649550500Z][com.docker.diagnose.exe][W] (c92cbf8e) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /hyperv/boot loader (533µs): Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:36.650057100Z][com.docker.diagnose.exe][I] (c92cbf8e-1) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:36.650057100Z][com.docker.diagnose.exe][W] (c92cbf8e-1) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:37.661360400Z][com.docker.diagnose.exe][I] (c92cbf8e-2) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:37.661360400Z][com.docker.diagnose.exe][W] (c92cbf8e-2) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:38.665275100Z][com.docker.diagnose.exe][I] (c92cbf8e-3) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:38.666241600Z][com.docker.diagnose.exe][W] (c92cbf8e-3) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (966 .5µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:39.669181300Z][com.docker.diagnose.exe][I] (c92cbf8e-4) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:39.669181300Z][com.docker.diagnose.exe][W] (c92cbf8e-4) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:40.679253200Z][com.docker.diagnose.exe][I] (c92cbf8e-5) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:40.680328700Z][com.docker.diagnose.exe][W] (c92cbf8e-5) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (943 .1µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:41.688973000Z][com.docker.diagnose.exe][I] (c92cbf8e-6) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:41.688973000Z][com.docker.diagnose.exe][W] (c92cbf8e-6) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:42.704416200Z][com.docker.diagnose.exe][I] (c92cbf8e-7) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:42.705171500Z][com.docker.diagnose.exe][W] (c92cbf8e-7) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (755 .3µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:43.714504300Z][com.docker.diagnose.exe][I] (c92cbf8e-8) cbf5fad9-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:43.715519200Z][com.docker.diagnose.exe][W] (c92cbf8e-8) cbf5fad9-com.docker.diagnose C<-S NoResponse GET /ping (986 .6µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [SKIP] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/c heck": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:43.731474800Z][com.docker.diagnose.exe][I] ipc.NewClient: 4dfc48b5-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-04-18T23:35:43.732112600Z][com.docker.diagnose.exe][I] (f9252837) 4dfc48b5-com.docker.diagnose C->S com.docker.service POST /wi ndowsfeatures/check: [VirtualMachinePlatform (Virtual Machine Platform)] [2023-04-18T23:35:43.733210300Z][com.docker.diagnose.exe][W] (f9252837) 4dfc48b5-com.docker.diagnose C<-S NoResponse POST /windowsfea tures/check (1.0914ms): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file speci fied. [2023-04-18T23:35:43.733210300Z][com.docker.diagnose.exe][I] (f9252837-1) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:43.733210300Z][com.docker.diagnose.exe][W] (f9252837-1) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:44.734905300Z][com.docker.diagnose.exe][I] (f9252837-2) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:44.735911100Z][com.docker.diagnose.exe][W] (f9252837-2) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (1.0 058ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:45.748220100Z][com.docker.diagnose.exe][I] (f9252837-3) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:45.749302900Z][com.docker.diagnose.exe][W] (f9252837-3) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (1.0 828ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:46.760341400Z][com.docker.diagnose.exe][I] (f9252837-4) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:46.760550800Z][com.docker.diagnose.exe][W] (f9252837-4) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (209 .4µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:47.767620100Z][com.docker.diagnose.exe][I] (f9252837-5) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:47.768577400Z][com.docker.diagnose.exe][W] (f9252837-5) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (957 .3µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:48.774795100Z][com.docker.diagnose.exe][I] (f9252837-6) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:48.774795100Z][com.docker.diagnose.exe][W] (f9252837-6) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:49.788143600Z][com.docker.diagnose.exe][I] (f9252837-7) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:49.789106300Z][com.docker.diagnose.exe][W] (f9252837-7) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (962 .7µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:50.800544100Z][com.docker.diagnose.exe][I] (f9252837-8) 4dfc48b5-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:50.800544100Z][com.docker.diagnose.exe][W] (f9252837-8) 4dfc48b5-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [FAIL] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pip e\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:50.803659400Z][com.docker.diagnose.exe][I] ipc.NewClient: 9567d438-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-04-18T23:35:50.803659400Z][com.docker.diagnose.exe][I] (0ed0e600) 9567d438-com.docker.diagnose C->S com.docker.service POST /wi ndowsfeatures/check: [Microsoft-Windows-Subsystem-Linux (Windows Subsystem for Linux)] [2023-04-18T23:35:50.804680400Z][com.docker.diagnose.exe][W] (0ed0e600) 9567d438-com.docker.diagnose C<-S NoResponse POST /windowsfea tures/check (1.021ms): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specif ied. [2023-04-18T23:35:50.804680400Z][com.docker.diagnose.exe][I] (0ed0e600-1) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:50.804680400Z][com.docker.diagnose.exe][W] (0ed0e600-1) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:51.810994700Z][com.docker.diagnose.exe][I] (0ed0e600-2) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:51.812083300Z][com.docker.diagnose.exe][W] (0ed0e600-2) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (1.0 886ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:52.821611300Z][com.docker.diagnose.exe][I] (0ed0e600-3) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:52.822556900Z][com.docker.diagnose.exe][W] (0ed0e600-3) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (945 .6µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:53.837961300Z][com.docker.diagnose.exe][I] (0ed0e600-4) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:53.839042800Z][com.docker.diagnose.exe][W] (0ed0e600-4) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (1.0 815ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:54.846639400Z][com.docker.diagnose.exe][I] (0ed0e600-5) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:54.847726700Z][com.docker.diagnose.exe][W] (0ed0e600-5) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (1.0 873ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:55.857768400Z][com.docker.diagnose.exe][I] (0ed0e600-6) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:55.858811900Z][com.docker.diagnose.exe][W] (0ed0e600-6) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (1.0 435ms): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:56.866134600Z][com.docker.diagnose.exe][I] (0ed0e600-7) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:56.866134600Z][com.docker.diagnose.exe][W] (0ed0e600-7) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (0s) : Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:35:57.874949800Z][com.docker.diagnose.exe][I] (0ed0e600-8) 9567d438-com.docker.diagnose C->S com.docker.service GET /p ing [2023-04-18T23:35:57.875929700Z][com.docker.diagnose.exe][W] (0ed0e600-8) 9567d438-com.docker.diagnose C<-S NoResponse GET /ping (979 .9µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [PASS] DD0029: is the WSL 2 Linux filesystem corrupt? [FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-04-18T23:35:58+00:00: parsing time "2023-04-18T23:35:58+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC" [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [FAIL] DD0005: is the user in the docker-users group? The user name could not be found. [PASS] DD0038: is the connection to Docker working? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [FAIL] DD0006: is the Docker Desktop Service responding? failed to ping com.docker.service with error: Get "http://ipc/ping": open \\ .\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-18T23:36:00.935029000Z][com.docker.diagnose.exe][I] ipc.NewClient: ed11f6d5-diagnose -> \\.\pipe\dockerBackendV2 Service [2023-04-18T23:36:00.935029000Z][com.docker.diagnose.exe][I] (df4235b8) ed11f6d5-diagnose C->S Service GET /ping [2023-04-18T23:36:00.935546500Z][com.docker.diagnose.exe][W] (df4235b8) ed11f6d5-diagnose C<-S NoResponse GET /ping (517.5µs): Get "h ttp://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [WARN] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [WARN] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/c heck": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [WARN] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pip e\dockerBackendV2: The system cannot find the file specified. [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [PASS] DD0029: is the WSL 2 Linux filesystem corrupt? [WARN] DD0035: is the VM time synchronized? parsing time output: 2023-04-18T23:35:58+00:00: parsing time "2023-04-18T23:35:58+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC" [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? Please note the following 23 warnings: 1 : The check: does the bootloader have virtualization enabled? Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: Th e system cannot find the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 2 : The check: does the bootloader have virtualization enabled? Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: Th e system cannot find the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 3 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 4 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 5 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 6 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 7 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 8 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 9 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 10 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 11 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 12 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 13 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 14 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 15 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 16 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 17 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 18 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 19 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 20 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 21 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 22 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2 : The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 23 : The check: is the VM time synchronized? Produced the following warning: parsing time output: 2023-04-18T23:35:58+00:00: parsing time "2023-04-18T23:35:58+00:00" as "2006 -01-02T15:04:05UTC": cannot parse "+00:00" as "UTC" The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly. Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists, try manually synchronizing the VM clock with "sudo hwclock -s". Please investigate the following 3 issues: 1 : The test: does the bootloader have virtualization enabled? Failed with: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot fin d the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 2 : The test: is the Virtual Machine Platform Windows Feature enabled? Failed with: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 3 : The test: is the Docker Desktop Service responding? Failed with: failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system canno t find the file specified. The Docker Desktop Service is needed to start the Docker engine. Open the list of Services and configure the Docker Desktop Service t o start automatically.

Steps to reproduce the behavior

startup Docker Desktop 4.18.0 in Windows 10;
execute “docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm secondstate/rust-example-hello:latest”
cloned this repo and build the docker image, execute "docker run --runtime=io.containerd.spin.v1 -p 3000:80 my-cms"

sam-thibault commented 1 year ago

Is this using the technical preview build? There is a special installer for previewing this feature.

rts-gordon commented 1 year ago

Hi @sam-thibault I installed Docker Desktop 4.18 for Windows 10, and turn on "Use containerd for pulling and storing images" to use WASM feature.

I didn't found the special installer for previewing WASM feature，would you like to give me a install URL? Thank you very much.

rdeveen commented 1 year ago

I can confirm the same in Docker Desktop version: 4.15.0 and Docker Desktop version: 4.16.3.

sam-thibault commented 1 year ago

The links to the Technical Preview 2 builds are further down the page on the blog post. These are the links: Mac (Intel) Mac (Arm) Linux (deb, Intel) Linux (deb, Arm) Linux (rpm, Intel) Linux (Arch) Windows

It does not like the links are in the right spot in that blog post, so I'll request the blog post be updated:

rdeveen commented 1 year ago

Ah, so wasmtime should only work with that specific version from the blog post and not with newer updates of Docker Desktop?

After installing the Windows version from the blog post both the wasmedge and the wasmtime gives this error:

docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm secondstate/rust-example-hello:latest
docker: Error response from daemon: Others("error setting up cgroups: error applying cgroup settings from oci spec: cgroup version v1: could not open cgroup file /sys/fs/cgroup/blkio/docker/4cad5c5e940115a9b2c3983b52d5b4d1639416d81f83b6f72b31742c45bf386e/blkio.weight: Permission denied (os error 13)"): unknown.

That looks the same as this issue: https://github.com/docker/roadmap/issues/467

sam-thibault commented 1 year ago

Yes, looks like the same issue.

sebagomez commented 1 year ago

The links mentioned above from this link are broken for me... I get 403 every time

I'm running Docker Desktop for Windows 4.19.0, do I still need the Tech Preview 2 to try wasmtime on WSL2?

This is the error I get

❯  docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm secondstate/rust-example-hello:latest
Unable to find image 'secondstate/rust-example-hello:latest' locally
84f52ad6497e: Download complete 
f1ac1f4d7141: Download complete 
14c421dda552: Download complete 
docker: Error response from daemon: failed to create task for container: failed to start shim: failed to resolve runtime path: runtime "io.containerd.wasmtime.v1" binary not installed "containerd-shim-wasmtime-v1": file does not exist: unknown.

EladAviczer commented 1 year ago

Linux (deb, Intel) link is broken for me. can someone send the correct link please ? @sam-thibault

meteatamel commented 1 year ago

Is --runtime=io.containerd.wasmtime.v1 supposed to work with latest Docker? Because I also get failed to start shim: failed to resolve runtime path: runtime "io.containerd.wasmtime.v1" binary not installed "containerd-shim-wasmtime-v1": file does not exist: unknown.

sam-thibault commented 1 year ago

In Docker Desktop 4.21, you can now select a setting to install the Wasm runtimes (spin, slight, wasmedge, wasmtime) when the containerd image store is enabled:

In Docker Desktop, navigate to the settings by clicking the gear icon.
Select the Features in development tab
Check the boxes for Use containerd for pulling and storing images and Enable Wasm.
Select Apply & restart.
When prompted for Wasm Runtimes Installation select Install.
After installation, these runtimes can be used to run Wasm workloads locally with the corresponding flags, for example: --runtime=io.containerd.spin.v1 --platform=wasi/wasm32

jhested commented 1 year ago

Maybe this could be of help for someone else, but I was unable to get this working when enabling both at the same time.

To get it working I disabled both features and restarted docker desktop.

After this I enabled containerd and clicked 'Apply & Restart' and then I enabled wasm.

That solved the issue for me

schristoff commented 1 year ago

@jhested I had the same issue where I applied them both at the same time. +1 to disabling both features, applying them one at a time.

craig-osterhout commented 1 year ago

Maybe this could be of help for someone else, but I was unable to get this working when enabling both at the same time.

To get it working I disabled both features and restarted docker desktop.

After this I enabled containerd and clicked 'Apply & Restart' and then I enabled wasm.

That solved the issue for me

+1 I ran into the same issue on 4.23

KEINOS commented 1 year ago

@jhested I was unable to get this working when enabling both at the same time.

To get it working I disabled both features and restarted docker desktop.

After this I enabled containerd and clicked 'Apply & Restart' and then I enabled wasm.

+1

Enabling one by one as mentioned worked for me. Thanks!

Docker Desktop 4.24.0 (122432)
macOS 12.7 Monterey

Before:

$ docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm hello-wasm
docker: Error response from daemon: failed to create task for container: failed to start shim: failed to resolve runtime path: runtime "io.containerd.wasmtime.v1" binary not installed "containerd-shim-wasmtime-v1": file does not exist: unknown.

$ docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm32 hello-wasm
Unable to find image 'hello-wasm:latest' locally
docker: Error response from daemon: failed to resolve reference "docker.io/library/hello-wasm:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed.
See 'docker run --help'.

After:

$ # wasi/wasm success!
$ docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm hello-wasm
Hello, World!

$ # wasi/wasm32 fails though
$ docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm32 hello-wasm
Unable to find image 'hello-wasm:latest' locally
docker: Error response from daemon: failed to resolve reference "docker.io/library/hello-wasm:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed.
See 'docker run --help'.

$ # Re-building with wasi/wasm32 then succeeds
$ docker buildx build --load --platform=wasi/wasm32 -t hello-wasm .
...
$ docker run --rm --runtime=io.containerd.wasmtime.v1 --platform=wasi/wasm32 hello-wasm
Hello, World!

docker / for-win