113xiaoji
113xiaoji
### Description When using logic from #3931, we discarded bindfd and adopted memfd. The pod has two containers: a main container and a sidecar. The request for the sidecar container...
### Description In the scenario where a single node concurrently deploys more than 100 containers, the call chain is kubelet -> containerd -> containerd-shim-runc-v2 ->runc root create -> runc init...
# Background When `bash` is absent, containers managed by `embedshim experience a hang, as illustrated by the following command: ```sh [root@master1 ~]# kubectl -it exec xxx-bqwbh -n manager -- bash...
# Background When loading the shim plugin, the following error is reported: ``` time="2024-01-21T11:07:44.731463684+08:00" level=warning msg="failed to load plugin io.containerd.runtime.v1.embed" error="program handle_sched_process_exit: apply CO-RE relocations: bad magic number '[159 235...
When using `crictl` to execute the `exec` command, there is an intermittent error reported: ``` execing command in container: error stream protocol error: invalid exit code value 4294967295 ``` The...
After running for a while, the containerd logs are continuously reporting an error: ``` level=error msg="RunPodSandbox for &PodSandboxMetadata{Name:kube-scheduler-master1,Uid:4bba31f5bbd08c1ecb43f3eeca03effb,Namespace:kube-system,Attempt:221,} failed, error" error="failed to create containerd task: failed to create init process:...
### Bug report criteria - [X] This bug report is not security related, security issues should be disclosed privately via [email protected]. - [X] This is not a support request or...