Attempting to start any container results in invalid argument

[GamePlayer-8]

Hello,

Whenever I'm trying to start new container with runc, I get exec /bin/sh: invalid argument.
In dmesg there is an error: get_file_caps: get_vfs_caps_from_disk returned -22 for /bin/sh.

Is there any way to disable capability check?

[cyphar]

The error is coming from the kernel, and you can only get -EINVAL from get_vfs_caps_from_disk if the file has a corrupted security.capabilities xattr. Can you share the image you're using? Normally /bin/sh doesn't have fscaps set.

A possible workaround would be the enable noNewPrivileges (in Docker and Podman this would be --security-opt no-new-privileges) as I think that would skip the code entirely, but you should figure out what is wrong with your image. Note that doing so will also disable setuid.

[GamePlayer-8]

I'm using any kind of image, really and it happens with all of them.

# podman run --network host --rm -it --security-opt no-new-privileges alpine:3.23
exec /bin/sh: invalid argument

Arch: aarch64