You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Hello, I'm on the very latest revisions of runc, and containerd (and since my config includes it, the hyperhq/shimv2 version of kata)
The CRI portion of my configuration file looks like this:
Description
Hello, I'm on the very latest revisions of
runc
, andcontainerd
(and since my config includes it, thehyperhq/shimv2
version of kata)The CRI portion of my configuration file looks like this:
ctr status
--runtime="io.containerd.runtime.v1.linux"
(legacy?)--runtime="io.containerd.runc.v1"
--runtime="io.containerd.kata.v2"
crictl status
--runtime="legacy"
(akaio.containerd.runtime.v1.linux
)--runtime="kata"
(akaio.containerd.kata.v2
)--runtime="runc"
(akaio.containerd.runc.v1
)When I fail to use
io.containerd.runc.v1
via CRI (--runtime="runc"
), I get these messages:failed to start sandbox container: failed to create containerd task: type with url containerd.linux.runc.RuncOptions: not found: unknown
Is this expected, or have I misconfigured something?
The text was updated successfully, but these errors were encountered: