What it is
Three things can stop io_uring_setup: a kernel older than 5.1 (ENOSYS), the kernel.io_uring_disabled sysctl from 6.6 (EPERM), and the seccomp profile of the container runtime (EPERM). Docker's default profile has blocked io_uring since 25.0.0 and containerd's followed, so a program that worked on a laptop fails in a container. This tool walks those steps in the order a real call meets them and names the first one that refuses.
When to use it
Use it when a database, proxy or runtime that uses io_uring prints Operation not permitted in Docker or Kubernetes, when you upgrade Docker across 25.0, or before relaxing a seccomp profile, to pick the narrowest fix.
Gotchas & limits
The version rules are marked to be verified until their official sources are re-read and dated. The release of containerd and CRI-O that changed the default profile is not recorded, so those cases stay uncertain. Unconfined and a host-wide sysctl change widen the attack surface for every process, not only your service; the fixes list the narrower options first.