-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
bug( containerd): Failed to create containerd task: failed to create shim task: OCI runtime create failed #2126
Comments
@Sandeepsac how do you reproduce this issue? |
@cartermckinnon , we getting in random node not for all nodes , for reference will share some error node events logs ![]() |
Getting this issue as well with:
|
@cartermckinnon to recreate run a pod like this:
|
@Sandeepsac / @venkatamutyala can you open an AWS support case for this if the impact is ongoing? I tried to reproduce it with the provided information but could not. You also initially mentioned it happened on random nodes so it would be helpful to get a broader sense of the environment this is being run in. |
@mselim00 we noticed this as well and aren't sure how this happened. I'll open a ticket and see what i can find. Maybe some upstream dependency was bad during our node provisioning? |
@venkatamutyala Do you know if the nodes running this are using containerd v1.7.23? There was a bug with leaking TTYs that was fixed in v1.7.25. |
Hi
What happened:
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: unable to freeze: unknown
Additionally, the sshd service on the node is repeatedly restarting. Logs show the following:
SshdRepeatedRestart: Systemd unit "sshd.service" has restarted (NRestarts 526 -> 533)
What you expected to happen:
1 The container should have been created successfully, and the specified command should have executed without errors.
2 .The sshd service should remain active and stable without repeated restarts in node
How to reproduce it (as minimally and precisely as possible):
Environment:
The text was updated successfully, but these errors were encountered: