5.4.2 tarball install fails to start container

[cyqsimon]

Using the 5.4.2 tarball install, starting any container fails:

# podman run --rm -it hello
WARN[0000] Using cgroups-v1 which is deprecated in favor of cgroups-v2 with Podman v5 and will be removed in a future version. Set environment variable `PODMAN_IGNORE_CGROUPSV1_WARNING` to hide this warning.
Error: crun: cannot resolve `null` under rootfs: No such file or directory: OCI runtime attempted to invoke a command that was not found

Going back to 5.4.1 tarball install and everything works as expected.

This is an older OS (RHEL8-like), so I'm stuck on cgroups V1. But I don't think this has anything to do with it.

[cyqsimon]

Sorry in advance for the very brief issue. I'm having the busiest day I've ever had in this job.

Let me know if this is not reproducible on RHEL8, and if so I'll provide more details.

[mgoltzsche]

Hi @cyqsimon, sorry to hear that it doesn't work for you - it works on my machine (Ubuntu 24.04 with cgroups v2) both with runc as well as with crun.

Apparently you're using crun as container runtime and crun is raising the error.
Can you try using runc instead? Does it work with runc by any chance?

OCI runtime attempted to invoke a command that was not found

Is it possible that an additional binary is required to run podman on a cgroups v1 host?

[mgoltzsche]

If using crun is important to you, I suggest to create a corresponding issue within the upstream podman project.