Open chenzhuofu opened 11 months ago
Could you please check the containerd
log and paste them here?
Could you please check the
containerd
log and paste them here?
Hi Mossaka,
I hadn't used containerd
to invoke containerd-wasmedged
. The later is an executable in /usr/local/bin/
.
Ah okay I misread it. I can verify that I could reproduce this error locally. Honestly I am not familiar with how the shared mode is implemented / used.
It looks like when you executed the binary, it tried to bind a socket at unix:///run/io.containerd.wasmwasi.v1/manager.sock
which was not found.
@cpuguy83 do you know this issue?
Try mkdir /run/io.containerd.wasmwasi.v1/
Try
mkdir /run/io.containerd.wasmwasi.v1/
That worked! I sucessfully started the containerd-wasmedged
after mkdir.
But now another problem is that when I started the daemon and executeed
sudo ctr run --rm --runtime=io.containerd.wasmedged.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm /wasi-demo-app.wasm echo 'hello'
,
it will timeouted and errored like,
ctr: failed to dial "/run/containerd/containerd.sock": context deadline exceeded
Could you please help me solve this?
Did you make sure that containerd is running in the background?
Sorry that I didn't start containerd by systemctl.
Then I started it and could execute sudo ctr run --rm --runtime=io.containerd.wasmedge.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm /wasi-demo-app.wasm echo 'hello'
in Normal mode and received the expected result ("hello\nexiting"
).
After that, I executed sudo containerd-wasmedged
in one bash and sudo ctr run --rm --runtime=io.containerd.wasmedged.v1 ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm /wasi-demo-app.wasm echo 'hello'
(for Shared mode) in another, but they all stuck.
Does Shared mode work well in your side? I don't know if I mistake something.
I followed the building instructions and installed the runwasi tools locally. The
make check
andmae test
executed successfully.Then I tried to use shared mode executing
containerd-wasmedged
to start daemon, but it errored as,Is it my mistake in operation or are there indeed some bugs? Thanks for attention.