v1.11.1 does not support Ubuntu 20.04 about crun HOT 8 CLOSED

I have too issue with crun 1.11.1 on Arch Linux, I downgrade crun from cache. Now I use 1.9.2 and all works well...

from crun.

I run in the same issue with my local Fedora installation. Since the last system update I can no longer start containers with podman, podman run always aborts with the following error message:

crun: {"msg":"read from sync socket","level":"error","time":"2023-11-01T23:59:24.863327Z"}: OCI runtime error

After downgrading crun from v1.11.1 to v1.8.3 everything works as before.

System information.

OS
  Fedora Linux 38 (Server Edition)
Hardware info
  Intel(R) Client Systems NUC8i5BEH
  Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz

BTW - Podman runs smoothly on my laptop with a similar software setup and same OS version.

from crun.

@raphaelheinrich do you have a reproducer?

from crun.

Hi @giuseppe

I found the cause of the problem for me. In an older Fedora version, I had activated cgroup v1 via Kernel parameter (systemd.unified_cgroup_hierarchy=0) in order to be able to use Docker. I have now reverted this change and podman works as usual again with version v1.11.1.

from crun.

crun should work fine with cgroup v1 too. What issue have you encountered?

from crun.

I can also recreate the problem on a second machine (OS: Fedora Linux 38 (Workstation Edition)). With active cgroup v1 I cannot start a container. But only when I run this as sudo, rootless also works fine with active cgroup v1.

I can say that the error only occurs for me when cgroup v1 is active and I start container as root.

In the log I see a Failed to create container: exit status 139 to that. I have attached the log entry for this.

cgroup_issue_protocol_log.txt

from crun.

cgroups V1 can not go away fast enough. :^(

from crun.

could you please verify if #1341 solves the problem you are seeing?

If you confirm it does, I can cut a new release with it

from crun.