OCI runtime error: crun: mount `mqueue` to `dev/mqueue`: No such device

[amo13]

With rootless podman, I do:

$ podman run --runtime krun --device /dev/fuse quay.io/podman/stable podman run alpine echo hello
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob sha256:6a0ac1617861a677b045b7ff88545213ec31c0ff08763195a70a4a5adda577bb
Copying config sha256:3cb067eab609612d81b4d82ff8ad71d73482bb3059a87b642d7e14f0ed659cde
Writing manifest to image destination
Error: OCI runtime error: crun: mount `mqueue` to `dev/mqueue`: No such device

$ podman run --runtime krun --device /dev/fuse quay.io/podman/stable podman run --mount type=bind,source=/dev/null,target=/dev/mqueue alpine echo hello
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob sha256:6a0ac1617861a677b045b7ff88545213ec31c0ff08763195a70a4a5adda577bb
Copying config sha256:3cb067eab609612d81b4d82ff8ad71d73482bb3059a87b642d7e14f0ed659cde
Writing manifest to image destination
hello

I have no idea what exactly this mqueue is used for anyway, but I thought I'd leave this here for others to find.

Is that behavior expected? Feel free to close if this is not a bug or if it does not belong in the repo.

[mtjhrc]

I tracked it down to this commit containers/libkrunfw@62444be Seems like it was intentionally disabled, assuming no-one would use it. I guess we can revert it.

Note though, that the container runtime itself doesn't need it - it just mounts it in case something in the container would need it. I suppose we could argue that the inner podman/crun could just not mount this by default if it's not available. The OCI spec doesn't actually require it - https://github.com/opencontainers/runtime-spec/blob/main/config-linux.md#default-filesystems