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
I am running containerd 2.0.0 with vmm-sandboxer and on top of it I am running k8s with cilium as CNI plugin.
when I start a simple redis pod with vmm runtime class , I see the following error
(combined from similar events): Failed to create pod sandbox: rpc error: code = Internal desc = failed to start sandbox "6b3ffcae3f0bda1df6c78856631d2b7732f3f4118d4706ddb6d34cc8c35c5348": failed to setup sandbox: rpc status: Status { code: UNKNOWN, message: "Others("Other: Failed to add address 2001:db8:7653:299:cafe::ac01: Received a netlink error message Not supported (os error 95)")", details: [], special_fields: SpecialFields { unknown_fields: UnknownFields { fields: None }, cached_size: CachedSize { size: 0 } } }
Host kernel is v6.2
What did you expect to happen?
start pod inside cloud hypervisor and have the pod up & running
How can we reproduce it (as minimally and precisely as possible)?
Cloud Hypervisor 41.0.0
Linux 6.2.0-060200-generic
start a single node k8s cluster with Kubeadm and install cilium cni
Anything else we need to know?
I am running static release binaries.
Dev environment
N/A
The text was updated successfully, but these errors were encountered:
What happened?
I am running containerd 2.0.0 with vmm-sandboxer and on top of it I am running k8s with cilium as CNI plugin.
when I start a simple redis pod with vmm runtime class , I see the following error
(combined from similar events): Failed to create pod sandbox: rpc error: code = Internal desc = failed to start sandbox "6b3ffcae3f0bda1df6c78856631d2b7732f3f4118d4706ddb6d34cc8c35c5348": failed to setup sandbox: rpc status: Status { code: UNKNOWN, message: "Others("Other: Failed to add address 2001:db8:7653:299:cafe::ac01: Received a netlink error message Not supported (os error 95)")", details: [], special_fields: SpecialFields { unknown_fields: UnknownFields { fields: None }, cached_size: CachedSize { size: 0 } } }
Host kernel is v6.2
What did you expect to happen?
start pod inside cloud hypervisor and have the pod up & running
How can we reproduce it (as minimally and precisely as possible)?
Cloud Hypervisor 41.0.0
Linux 6.2.0-060200-generic
start a single node k8s cluster with Kubeadm and install cilium cni
Anything else we need to know?
I am running static release binaries.
Dev environment
N/A
The text was updated successfully, but these errors were encountered: