Description
Hi, I've encountered a weird issue during cluster creation where some nodes frequently experience the following situations:
-
level=error msg="Container creation error: runc create failed: unable to start container process: exec: \"/bin/prometheus-config-reloader\": permission denied"
-
level=error msg="Container creation error: runc create failed: unable to start container process: exec: \"/cluster/kube-apiserver-operator\": executable file not found in $PATH"
-
level=error msg="Container creation error: runc create failed: unable to start container process: exec: \"/usr/bin/pod\": stat /usr/bin/pod: no such file or directory"
These container creation failures occur when non-root users execute the files, which have executable permissions set to 755.
What puzzles me most is that after restarting the pod, the containers are created successfully. This issue only occurs repeatedly during the cluster creation process.
Steps to reproduce the issue
The problem occurs frequently after upgrading cri-o from version 1.25.4 to 1.29.13
crio version 1.25.4
Version: 1.25.4
GitCommit: unknown
GitCommitDate: unknown
GitTreeState: clean
GoVersion: go1.18.4
crio version 1.29.13
Version: 1.29.13
GitCommit: unknown
GitCommitDate: unknown
GitTreeState: clean
GoVersion: go1.21.11
Describe the results you received and expected
Container creation should normal.
What version of runc are you using?
runc --version
runc version 1.1.12
spec: 1.0.2-dev
go: go1.18.4
libseccomp: 2.5.2
Host OS information
No response
Host kernel information
uname -a
5.15.131-18.cl9.x86_64