-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod without command or arguments is running forever #9648
Comments
Output of Show kata-collect-data.sh details
Meta detailsRunning Runtime
Runtime is
|
Although you do not specify a command, the container image may have a default command or entrypoint. All different images may behave differently. How does this test perform on the runC runtime? |
Hi @lifupan I'm using the default alpine image without any customisation. The default command/entrypoint should be On the runC runtime, the pod finishes than fails immediately
|
I researched this problem and found that for images like alpine, the stdin passed by containerd is empty when the terminal is not explicitly used. For runC, when it creates the container process, it changes the stdin of the container process. It is set to /dev/null, and the init process of the container is sh. Because stdin is /dev/null, the process will automatically exit after starting, so the runC container will also automatically exit. But for kata, when kata creates the container process, it does not consider whether the stdin passed by containerd is empty. If the terminal is not enabled, kata-agent will set the stdin of the container process to a fifo file, so The container process sh started by kata will not exit automatically. |
Get your issue reviewed faster
To help us understand the problem more quickly, please do the following:
kata-collect-data.sh
script, which is installed as part of Kata Containersor
kata-containers.collect-data
, which is installed as part of the Kata Containerssnapcraft package.
see comment below ⬇️
Description of problem
I created a pod with kata-qemu runtimeclass. This pod is only running an alpine without any command/arguments
The pod is stuck in running state forever
I checked the processes inside the container, but I'm not seeing anything strange
Expected result
I expected the pod will fail immediately
Actual result
the pod is running forever
The text was updated successfully, but these errors were encountered: