I thought runc was fixed to produce ENOSYS by now for unknown syscalls to avoid that mess. We can't have every glibc update breaking containers like this...
405 clone3({flags=CLONE_VM|CLONE_VFORK, exit_signal=SIGCHLD, stack=0x7fc77e3d3000, stack_size=0x9000}, 88) = -1 EPERM (Operation not permitted)
Not sure if it applies to crun, someone check with that :D
I thought runc was fixed to produce ENOSYS by now for unknown syscalls to avoid that mess. We can't have every glibc update breaking containers like this...
405 clone3( {flags= CLONE_VM| CLONE_VFORK, exit_signal= SIGCHLD, stack=0x7fc77e3 d3000, stack_size=0x9000}, 88) = -1 EPERM (Operation not permitted)
Not sure if it applies to crun, someone check with that :D