Replies: 4 comments 1 reply
-
What is your distro? |
Beta Was this translation helpful? Give feedback.
-
It supports CONFIG_IPC_NS because I use docker and runc 1.0-rc10 to run successfully env: Kylin Linux Advanced Server V10 (Lance) ,4.19.90-52.23.v2207.ky10.x86_64 |
Beta Was this translation helpful? Give feedback.
-
What does |
Beta Was this translation helpful? Give feedback.
-
It appears you're using a pre-1.1 version of runc (that error message was changed in e918d02, in 2021). Can you try to reproduce this issue with the latest version of runc (runc 1.1.9) or on the Looking at whether the error comes from, it seems that you are creating a container using the namespace path of another process, and given the other information you have provided it seems that the process is dead so the namespace path doesn't exist when runc is trying to join it. It also looks like you're using Kubernetes, not runc directly (information that would've been helpful to include in the original issue description). Can you provide some more information as to your setup and what you're trying to do when you get the error? |
Beta Was this translation helpful? Give feedback.
-
Description
container create failed: container_linux.go:338: creating new parent process caused "container_linux.go:1897: running lstat on namespace path "/proc/63538/ns/ipc" caused "lstat /proc/63538/ns/ipc: no such file or directory""
Steps to reproduce the issue
Describe the results you received and expected
container create failed
What version of runc are you using?
latest
Host OS information
No response
Host kernel information
4.19.90
Beta Was this translation helpful? Give feedback.
All reactions