-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Description
/kind feature
Description
Adding support for the shimv2 interface https://alibaba-cloud.medium.com/cri-and-shimv2-a-new-idea-for-kubernetes-integrating-container-runtime-ab8d22f5716b, useful for example for Kata Containers version 2.0 which no longer supports the earlier CRI interface (see kata-containers/kata-containers#1133 (comment)).
Steps to reproduce the issue:
podman run -it --runtime kata fedora bash
That works with kata being kata-runtime (Kata Containers version 1.0) but not with containerd-shim-kata-v2 (Kata Containers version 2.0).
Output of podman version:
Version: 2.1.1
API Version: 2.0.0
Go Version: go1.15.2
Built: Wed Oct 7 18:21:20 2020
OS/Arch: linux/amd64
Output of podman info --debug:
host:
arch: amd64
buildahVersion: 1.16.1
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: Unknown
path: /usr/libexec/podman/conmon
version: 'conmon version 2.0.11-dev, commit: 77f4a5131bfc344ab4485cd3f1e4644bfa2122e2'
cpus: 12
distribution:
distribution: fedora
version: "33"
eventLogger: journald
hostname: turbo.dinechin.lan
idMappings:
gidmap: null
uidmap: null
kernel: 5.9.8-200.fc33.x86_64
linkmode: dynamic
memFree: 1521201152
memTotal: 33522884608
ociRuntime:
name: crun
package: crun-0.15.1-1.fc33.x86_64
path: /usr/bin/crun
version: |-
crun version 0.15.1
commit: eb0145e5ad4d8207e84a327248af76663d4e50dd
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
os: linux
remoteSocket:
path: /run/podman/podman.sock
rootless: false
slirp4netns:
executable: ""
package: ""
version: ""
swapFree: 99739828224
swapTotal: 103846764544
uptime: 72h 44m 18.82s (Approximately 3.00 days)
registries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- registry.centos.org
- docker.io
store:
configFile: /etc/containers/storage.conf
containerStore:
number: 1
paused: 0
running: 1
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mountopt: nodev,metacopy=on
graphRoot: /var/lib/containers/storage
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "true"
imageStore:
number: 5
runRoot: /var/run/containers/storage
volumePath: /var/lib/containers/storage/volumes
version:
APIVersion: 2.0.0
Built: 1602087680
BuiltTime: Wed Oct 7 18:21:20 2020
GitCommit: ""
GoVersion: go1.15.2
OsArch: linux/amd64
Version: 2.1.1
Package info (e.g. output of rpm -q podman or apt list podman):
podman-2.1.1-12.fc33.x86_64
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
No (but I don't expect the latest has the fix, not having seen a mention of "shim v2" in the issues)
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical with Kata
Note
Kata Containers is considering doing the opposite, which is to restore the original CLI commands, see kata-containers/kata-containers#722. However, that would lead to a more inefficient setup (multiple shims), so the shimv2 interface remains interesting in the long run.