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.

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

Start by reproducing the reported failure with runc 1.2.9, 1.3.4, or 1.4.1: restart containerd, create a Kubernetes pod with tty:true, and observe whether shim container creation fails. Compare the result with the expected successful pod creation; the issue does not name a source file or test, so further investigation is needed to locate the failing runtime path.