Comment 11 for bug 1943049

Just to be clear, this is a container host bug which needs to be fixed. glibc works fine on real Linux kernels with and without clone3 support.

There is *supposed* to be a generic fix for this in docker and runc, but that broke temporarily upstream when support for other system calls (with higher system call numbers than clone3) was added. As far as I know, podman does not have the generic fix, so it currently needs to be updated for each new system call individually. (None of this depends on the system calls actually implemented in the host kernel, just to be clear.)

From a philosophical perspective, I also object to the notion that the container hosts developers get to define the Linux system call interface. That should be up to Linux maintainers in collaboration with userspace developers.