-
Notifications
You must be signed in to change notification settings - Fork 95
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
child process gets killed by SIGKILL after using cgroup v1 API #40
Comments
@cpuguy83 and I briefly investigated this issue and we think it is highly possibly that the issue is caused by cgroup setup. The environment I am in when encountered this issue is using cgroup v1:
|
For cgroup v1, I didn't get the cgroup test to pass. Adding a bit of logging, it seems setting the
I tried creating a cgroup directory by hand, but writing to the |
This might no longer be an issue as we are moving to use youki's APIs. I am okay to close this one if #142 merges in. |
Containerd Log
Notice that there is a log message says "[INFO] child 1794 killed by signal SIGKILL, dumped: false"
How to reproduce?
Setup a k3d cluster image follow the steps in https://github.com/deislabs/containerd-wasm-shims/tree/main/deployments/k3d. Replace the spin & slight shim with wasmtime shim in "config.toml.tmpl"
Once the k3d cluster image is created, we can create a k3d cluster by running
k3d cluster create k3s-default --image k3swithshim --api-port 6550 -p "8081:80@loadbalancer" --agents 1
Then apply the following workloads
The text was updated successfully, but these errors were encountered: