Comment 8 for bug 1916485

Yes, it's a seccomp issue that needs to be fixed on the container host.

There's a generic kludge here: https://github.com/opencontainers/runc/pull/2750

Recent docker/podman version be okay as well, but the fix (logically, not explicitly) depends on other package updates too (e.g., libseccomp).

Most container hosts on offer allow disabling seccomp filters in some way, but that's not entirely standardized.