In my test, the versions 1.2.8-1.4.1 of runc do not support the parameter "tty:true" for Kubernetes pods. The containers remain in the process of creation.

[wqzgithub]

Description

In my test, the versions 1.2.9 1.3.4 1.4.1 of runc do not support the parameter "tty:true" for Kubernetes pods. The containers remain in the process of creation.

Steps to reproduce the issue

1.Replace the runc version
2.Restart containerd
3.Create a pod and add "tty:true" to verify the operation.

Describe the results you received and expected

shim container created faild

What version of runc are you using?

runc 1.2.9 1.3.4 1.4.1 amd 64
kubernetes：1.33.7

Host OS information

$ cat /etc/os-release
NAME="Kylin Linux Advanced Server"
VERSION="V10 (Halberd)"
ID="kylin"
VERSION_ID="V10"
PRETTY_NAME="Kylin Linux Advanced Server V10 (Halberd)"
ANSI_COLOR="0;31"

$ nkvers
############## Kylin Linux Version #################
Release:
Kylin Linux Advanced Server release V10 (Halberd)

Kernel:
4.19.90-89.11.v2401.ky10.x86_64

Build:
Kylin Linux Advanced Server
release V10 SP3 2403/(Halberd)-x86_64-Build20/20240426
#################################################
$ uname -a
Linux ZKV-UETPREGMAS02-P 4.19.90-89.11.v2401.ky10.x86_64 #1 SMP Tue May 7 18:33:01 CST 2024 x86_64 x86_64 x86_64 GNU/Linux

Host kernel information

No response

[lifubang]

Do you mean the pod got stuck, or did it fail to be created? If there are any error logs, could you please share them?

[lifubang]

This issue doesn’t reproduce in my cluster with the same version.

[wqzgithub]

Before this issue arose, I performed a Kubernetes version upgrade. The previous Kubernetes version was 1.31 and the runc version was 1.1.14.

The pod has always been in the "ContainerCreating" state, and the "describe" command has no error events. By using "crictl ps -a" to find the container, it is in the "created" state. By inspecting it, a "shim task" error can be seen. When I switched the runc version to 1.1.14, it started to work normally,
My version of containerd is 1.7.29

[wqzgithub]

On containerd, I enabled the debug true check. However, I didn't see any obvious related logs. So I suspected it was a compatibility issue with runc. After reverting to runc, everything worked properly.

[kolyshkin]

I'm pretty sure this is something not related to terminal. Maybe higher memory limits are needed, or something else. You need to find out the exact reason why your containers can't be created; this is usually printed in an error by runc.

Also please check the kernel logs for OOM messages, and system logs in general.