You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I attempting to configure stargz-snapshotter with selinux enabled and running into issues with pods that would otherwise run being rejected by selinux.
with the following error Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/963577/ns/ipc: no such file or directory: unknown.
I understand that this is due to a selinux violation as when accessing the node I see the following:
However deploying the same pod configuration without stargz enabled in containerd (but selinux enabled, config provided below) results in the pod being deployed all okay.
Am I doing something obviously wrong when configuring containerd with estargz? Any pointers would be greatly appreciated!
If there is anything else I can provide to help please do let me know. I can give full dumps of the containerd config for example, but for now was trying to filter out any noise to make it as easy as possible for review
Cheers,
Jack
The text was updated successfully, but these errors were encountered:
Hey,
I attempting to configure stargz-snapshotter with selinux enabled and running into issues with pods that would otherwise run being rejected by selinux.
My containerd configuration is as follows:
Attempting to run the following pod on a node with stargz configured results in the pod going into
CrashLoopBackoff
with the following error
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/963577/ns/ipc: no such file or directory: unknown
.I understand that this is due to a selinux violation as when accessing the node I see the following:
However deploying the same pod configuration without stargz enabled in containerd (but selinux enabled, config provided below) results in the pod being deployed all okay.
Am I doing something obviously wrong when configuring containerd with estargz? Any pointers would be greatly appreciated!
If there is anything else I can provide to help please do let me know. I can give full dumps of the containerd config for example, but for now was trying to filter out any noise to make it as easy as possible for review
Cheers,
Jack
The text was updated successfully, but these errors were encountered: