Comment 36 for bug 2056442

There was no clear indication which running kernel was used during the verifications, so I did it:

Using the Dockerfile from the test plan:
FROM ubuntu:noble
RUN apt install -U systemd -y
CMD ["/lib/systemd/systemd"]

And building with "podman build -t systemd ."

a) 5.15.0-105 kernel (jammy GA kernel)
crun 0.17+dfsg-1.1 from jammy fails (odd, I thought it was unaffected):

$ podman run --systemd always systemd
Error: OCI runtime error: chmod `run/shm`: Operation not supported

crun 0.17+dfsg-1.1ubuntu0.1 from jammy-proposed works:

$ podman run --systemd always systemd
(nothing here)

In a separate terminal we can see it's running:
$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b2decb3d2820 localhost/systemd:latest /lib/systemd/syst... 34 seconds ago Up 34 seconds ago flamboyant_hertz

b) Jammy HWE kernel
$ uname -r
6.5.0-34-generic

crun 0.17+dfsg-1.1 from jammy fails:
$ podman run --systemd always systemd
Error: OCI runtime error: chmod `run/shm`: Operation not supported

crun 0.17+dfsg-1.1ubuntu0.1 from jammy-proposed works:
$ podman run --systemd always systemd
(nothing here)

In another terminal:
$ podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
867d113be7a3 localhost/systemd:latest /lib/systemd/syst... 2 seconds ago Up 2 seconds ago confident_mirzakhani