不能进入k3s的POD内,什么原因呢?

$ kubectl exec -it web-6596ff9565-nrk24 – sh
error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec “ac9fada34dc7646a4ce44c4cca2d24264a32f5f3eab65597d4153a60b4e3cdb4”: OCI runtime exec failed: exec failed: unable to start container process: open /dev/pts/0: operation not permitted: unknown

版本信息
$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:“1”, Minor:“24”, GitVersion:“v1.24.3+k3s1”, GitCommit:“990ba0e88c90f8ed8b50e0ccd375937b841b176e”, GitTreeState:“clean”, BuildDate:“2022-07-19T01:10:03Z”, GoVersion:“go1.18.1”, Compiler:“gc”, Platform:“linux/amd64”}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:“1”, Minor:“24”, GitVersion:“v1.24.3+k3s1”, GitCommit:“990ba0e88c90f8ed8b50e0ccd375937b841b176e”, GitTreeState:“clean”, BuildDate:“2022-07-19T01:10:03Z”, GoVersion:“go1.18.1”, Compiler:“gc”, Platform:“linux/amd64”}

k3s v1.24.3+k3s1 使用的 runc 版本为 v1.1.3,而这个版本的 runc 因为一个 bug 导致了上述问题,具体原因和解决方法可以参考:[1.1] Fix failed exec after systemctl daemon-reload (regression in 1.1.3) by kolyshkin · Pull Request #3554 · opencontainers/runc · GitHub

谢谢!