search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.85k stars 285 forks source link

WASM Preview error? #13070

Open johnkennyuk opened 1 year ago

johnkennyuk commented 1 year ago

Actual behavior

WASM EXAMPLE throws this error when trying to run: - Error response from daemon: failed to start shim: failed to resolve runtime path: runtime "io.containerd.wasmedge.v1" binary not installed "containerd-shim-wasmedge-v1": file does not exist: unknown

Expected behavior

I was expecting the example to deploy.

Information

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

[PASS] DD0027: is there available disk space on the host? [SKIP] DD0028: is there available VM disk space? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0020: is the Hyper-V Windows Feature enabled? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [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] 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? [PASS] DD0006: is the Docker Desktop Service responding? [FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1 [2022-11-14T10:28:59.455199900Z][com.docker.diagnose.exe][I] ipc.NewClient: df7b1665-diagnose-network -> \.\pipe\dockerDiagnosticd diagnosticsd [common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK() [ common/pkg/diagkit/gather/diagnose/network.go:34 +0xd9 [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1ae4360) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x1ae4360) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1ae4360) [ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1ae4360, 0xc000259728) [ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1ae4960, 0xc000259728) [ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52 [common/pkg/diagkit/gather/diagnose.walkOnce(0x14829c0?, 0xc0005bf890) [ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x1ae4960, 0x1a3cad0000000000?, {0xc0005bfb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4 [main.checkCmd({0xc0001963b0?, 0xc0001963b0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:133 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:99 +0x287 [2022-11-14T10:28:59.456200200Z][com.docker.diagnose.exe][I] (69d28d6f) df7b1665-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["100.95.179.30","10.10.10.3","192.168.55.51","172.25.224.1","172.23.96.1","172.22.208.1","172.19.240.1","172.20.112.1","172.24.192.1"]} [2022-11-14T10:29:00.032641600Z][com.docker.diagnose.exe][W] (69d28d6f) df7b1665-diagnose-network C<-S 240a643c-diagnosticsd POST /check-network-connectivity (576.9417ms): failed to ping host: exit status 1

[SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0020: is the Hyper-V Windows Feature enabled? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [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? [WARN] DD0032: do Docker networks overlap with host IPs? network portainer_portainer-docker-extension-desktop-extension_default has subnet 172.20.0.0/16 which overlaps with host IP 172.20.112.1

Steps to reproduce the behavior

I am using the articles from here https://docs.docker.com/desktop/wasm/#running-a-wasm-application-with-docker-compose

with this app as is https://docs.docker.com/desktop/wasm/#running-a-wasm-application-with-docker-compose

alkreddy commented 1 year ago

I am facing same error. Any help?

NetanelBollag commented 1 year ago

Me too

Evanfeenstra commented 1 year ago

u need docker desktop 4.15 https://docs.docker.com/desktop/release-notes/

alkreddy commented 1 year ago

Thanks. I upgraded docker desktop to latest (4.15) and this did work for me

docker-robott commented 1 year ago

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

WeixinX commented 1 year ago

I would like to know whether Docker Engine 24.0.0-beta.1 can work properly. Because it outputs the same error as above. Please tell me how to find the relevant information, thank you~

pramineni01 commented 1 year ago

Worked when i followed this link: Turn on the Docker+Wasm integration How to enable containerd image store feature

sdkim81 commented 3 months ago

I'm facing same error and IMO below call stack is a hint for this issue. 

[2024-05-30T05:17:46.595753440Z][lifecycle-server.ipc][W] (a5874962) 816e604d-lifecycle-server S->C 6816e411-WasmManager POST /<US
ER>/runtimes (1.809136933s): GET https://index.docker.io/v2/rumpl/containerd-wasi-shims/manifests/sha256:88a3cb85e329a6e367565531f
a4de92c164c01b8730b925a9a721896130c6ba1: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by aut
henticating and upgrading: https://www.docker.com/increase-rate-limit
[linuxkit/pkg/init/pkg/lifecycle-server/handlers/<USER>.go:22 github.com/docker/pinata/linuxkit/pkg/init/pkg/lifecycle-server/hand
lers.InstallWasmRuntimesHandler()
[common/pkg/ipc/server.go:258 github.com/docker/pinata/common/pkg/ipc.(*server).Run.(*server).wrapHandlerFunc.func7()
[github.com/labstack/echo/v4@v4.11.4/echo.go:582 github.com/labstack/echo/v4.(*Echo).add.func1()
[common/pkg/ipc/server.go:266 github.com/docker/pinata/common/pkg/ipc.(*server).unwrapHandlerFunc.func1()
[common/pkg/telemetry/middleware/middleware.go:32 github.com/docker/pinata/common/pkg/telemetry/middleware.Middleware.func1.1.2()
[go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho@v0.46.1/echo.go:93 go.opentelemetry.io/contrib/inst
rumentation/github.com/labstack/echo/otelecho.Middleware.func1.1()
[common/pkg/telemetry/middleware/middleware.go:34 github.com/docker/pinata/common/pkg/telemetry/middleware.Middleware.func1.1()
[common/pkg/ipc/server.go:275 github.com/docker/pinata/common/pkg/ipc.(*server).Use.(*server).wrapInterceptor.func1.1()
[common/pkg/ipc.(*server).Run.RecoverWithConfig.func5.1()
[github.com/labstack/echo/v4@v4.11.4/echo.go:669 github.com/labstack/echo/v4.(*Echo).ServeHTTP()
[net/http/server.go:3137 net/http.serverHandler.ServeHTTP()
[net/http/server.go:2039 net/http.(*conn).serve()
[runtime/asm_amd64.s:1695 runtime.goexit()

My network is behind of proxy so there is pull limit rate issue and I authenticated with my account but there is still limit rate issue. Is there any way to use local registry image or authenticated token (for my own pull limit rate) ?