Comment 18 for bug 2056442

Hi Faustin,

#12 This bug is a little bit about which image to use, because not every image is triggering this bug. First, systemd must be present in the image. Second, some images are known to not trigger it, e.g. Debian older than 12, Fedora, Rocky, the whole RedHat world does not show the behaviour.

#16 I used the --systemd always switch in #8 because it makes my life easier not because it is strictly necessary. If I did not use it I had to specify --tmpfs and volume for /sys/fs/cgroup manually (it does a bunch foo magic in the background), see podman-run(1). But, of course, the complexity grows with rootful vs. rootless or cgroups v1 vs. cgroups v2 and stuff. It's easy to mix issues.

FWIW, here are my references for this bug.

https://noobient.com/2023/11/15/fixing-ubuntu-containers-failing-to-start-with-systemd/
https://github.com/containers/crun/issues/1308
https://github.com/containers/crun/pull/1309