Podman doesn't work on 22.10 (worked on 22.04 LTS)

[Peter]

Podman 3.4.4, which is the version available both in 22.10 and 22.04, no longer works after upgrading to 22.10:

```
$ podman run -it --rm docker.io/bash # Or any other image..
Error: OCI runtime error: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF
```

On the same machine, Docker works.

## WORKAROUNDS:

- As noted below by @blk-u, run podman as root
- Alternatively, as noted by @enokijn, install crun

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Peter (vp2177)]

It looks like Debian testing (and unstable) have Podman 3.4.7, which is newer. Perhaps syncing the Ubuntu package would resolve the issue?

[Brant Knudson (blk-u)]

I also hit this after upgrading to 22.10.
Not noted in the bug description is that podman works as root but not as a user.

Some discussion here https://groups.google.com/g/linux.debian.bugs.dist/c/pnQcz8V6dQ8 says it's fixed with podman 4.1.

[Erik van Konijnenburg (ekonijn)]

The previous comment refers to https://groups.google.com/g/linux.debian.bugs.dist/c/pnQcz8V6dQ8

which notes upstream issue https://github.com/containers/podman/issues/13731

which notes cause is systemd v250,
https://github.com/systemd/systemd/issues/22437

one upstream comment explains why the change in systemd was made:
https://github.com/containers/podman/issues/13731#issuecomment-1094253537

"The change in systemd was introduced so that user services would be
more likely to be killed by the OOM killer than system services or the
managers themselves. It did cause at least one other issue in dbus-daemon
but the argument was that processes without privileges shouldn't attempt
to lower their score."

The fix is here, part of podman 4.1
https://github.com/containers/podman/pull/13765/commits/164b64ea3baa8502a23fc0c7674f4a7e60507aa0

this is a small commit, but it does not apply cleanly to 3.4.4, and
anyway I'm not familiar enough with golang to attempt building the package
from source.

A workaround is to install crun(1) in addition to runc(1).

Podman will then use crun(1) in preference to runc(1), and will be able
to start images.

You could automate that by replacing the "crun | runc" dependency of
podman by a simple "crun". The downside of that approach is that this
leaves you with a crun(1) that would be redundant once ubuntu upgrades
to podman 4.X, but at least you have a podman that runs out of the box.

[Peter (vp2177)]

Podman works again in Ubuntu 23.04