containerd / containerd/nerdctl

nerdctl oci hook failed with wasm image (`containerd-shim-wasmtime-v1`)

Open
#4,074 8 comments 1 reaction 0 assignees View on GitHub
bug expert kind/external
Dominant language
Go
Stars
10.4k
Forks
826
Avg merge
1d 23h
Merged PRs (30d)
44

Description

### Description

To reproduce, you can install a wasmtime shim on your PATH named `containerd-shim-wasmtime-v1` from https://github.com/containerd/runwasi/releases/tag/containerd-shim-wasmtime%2Fv0.5.0.

And then try to run with the following image: `ghcr.io/containerd/runwasi/wasi-demo-app:latest` and you will see

```console
sudo nerdctl run --rm --runtime=io.containerd.wasmtime.v1 --debug ghcr.io/containerd/runwasi/wasi-demo-app:latest testwasm /wasi-demo-app.wasm echo 'hello'
DEBU[0000] verifying process skipped
DEBU[0000] generated log driver: binary:///usr/local/bin/nerdctl?_NERDCTL_INTERNAL_LOGGING=%2Fvar%2Flib%2Fnerdctl%2F1935db59
DEBU[0000] detected 127.0.0.53 nameserver, assuming systemd-resolved, so using resolv.conf: /run/systemd/resolve/resolv.conf
WARN[0000] cannot set cgroup manager to "systemd" for runtime "io.containerd.wasmtime.v1"
DEBU[0000] remote introspection plugin filters filters="[type==io.containerd.snapshotter.v1, id==overlayfs]"
FATA[0000] failed to create shim task: failed to create container: hook command exited with non-zero exit code: 1: unknown

```

### Steps to reproduce the issue

1.
2.
3.

### Describe the results you received and expected

The expected result should be "hello" printed and the container exsited.

### What version of nerdctl are you using?

nerdctl version 2.0.4

### Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

### Host information

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.