Parikshit Patil (परिक्षित पाटील)

I have also expected an example project created using all functionalities.

[runsc.log.20241006-163925.472943.create.txt](https://github.com/user-attachments/files/17270265/runsc.log.20241006-163925.472943.create.txt) [runsc.log.20241006-163925.472943.gofer.txt](https://github.com/user-attachments/files/17270266/runsc.log.20241006-163925.472943.gofer.txt) [runsc.log.20241006-163925.472943.boot.txt](https://github.com/user-attachments/files/17270267/runsc.log.20241006-163925.472943.boot.txt) [runsc.log.20241006-163925.872791.start.txt](https://github.com/user-attachments/files/17270268/runsc.log.20241006-163925.872791.start.txt) [runsc.log.20241006-163952.772808.create.txt](https://github.com/user-attachments/files/17270269/runsc.log.20241006-163952.772808.create.txt) [runsc.log.20241006-163952.832728.gofer.txt](https://github.com/user-attachments/files/17270270/runsc.log.20241006-163952.832728.gofer.txt) [runsc.log.20241006-163952.832728.start.txt](https://github.com/user-attachments/files/17270271/runsc.log.20241006-163952.832728.start.txt)

#### From host  #### With `runc` 

##### Logs from containerd ``` Oct 06 17:12:11 ip-172-21-148-200.eu-central-1.compute.internal containerd[3328]: time="2024-10-06T17:12:11.657866697Z" level=info msg="Connect containerd service" Oct 06 17:12:11 ip-172-21-148-200.eu-central-1.compute.internal containerd[3328]: time="2024-10-06T17:12:11.657899997Z" level=info msg="using legacy CRI server" Oct 06 17:12:11 ip-172-21-148-200.eu-central-1.compute.internal...

@ayushr2 It isn't getting stuck now. Thanks 👍🏼. One container started successfully, but after that, **all containers remained running**. They should exit after displaying the output of the `nvidia-smi` command....

#11003 did not work. there were no `runsc.log.*.wait.txt` or `runsc.log.*.delete.txt` log files generated. Below got `runsc.log.*.delete.txt` maybe because I tried to delete the pod and it got hanged for delete...

Yes , it does not occur with runc. I have added screenshot of it in my previous comment also added logs of containerd with runc.

Hey @zkoopmans , so I've followed the same doc to get Gvisor and the containerd up and running, which is working out great so far... but when I try to...

Hi @ayushr2, are you able to get output from `nvidia-smi`? did you added exec script in `/etc/nvidia-container-runtime/config.toml`? I tried changing `runtime_type` in `/etc/containerd/config.toml` ``` FATA[0003] Starting the container "cda53658e7ac6e52128fd85700da99f8e20cfea10fea1175f01f920c4d524ba0" failed:...

Hi @ayushr2, Thank you so much! It's working now. I have a question though—don't you think the `binary_name` in the file `/etc/containerd/runsc.toml` could also affect non-GPU workloads? Shouldn't it be...