Hello @bish!
Tess is out of the office today. The nsjail is built out inside the 'Code Executor' container, I would see if the log tools for that container has more details on why it is giving the 'Couldn't launch the child process' error.
Unfortunately I haven't seen this bug before.
Maybe some other users might be able to chime in.
For troubleshooting helm/EKS/container bugs, the debugging method usually involves going through any and all changes made from the original template cloned from github to see where the code might have diverged from what should be the working default.
This would be much easier to do during our office hours as we will need to be asking to see helm charts and logs, with lots of back and forth which is easier to do live 