EDIT: that was a response to #1, I did not refresh the launchpad page before posting.
I am not sure that this is something easy to find (at least I don't know how to proceed). And above all, my understanding is that the problem seems to be related to the "old" crun version and quite new kernels (6.5).
Also, 22.04 (and Bullseye) comes with crun 0.17 and there is a huge gab with the next release 23.04 that seems to come with crun 1.8-1 (same version in Bookworm).
Anyway, after testing, I can't reproduce the problem on a generic cloud-init image, so that can maybe help?
Here is my test setup:
- Ubuntu 22.04 KVM/Qemu started from generic cloud-init images (amd64);
- kernel upgraded to 6.5.0-1015-azure;
- podman/crun installed from ubuntu repos.
Following command works:
$ podman run --rm -d ghcr.io/fauust/docker-systemd:debian-11
EDIT: that was a response to #1, I did not refresh the launchpad page before posting.
I am not sure that this is something easy to find (at least I don't know how to proceed). And above all, my understanding is that the problem seems to be related to the "old" crun version and quite new kernels (6.5).
Also, 22.04 (and Bullseye) comes with crun 0.17 and there is a huge gab with the next release 23.04 that seems to come with crun 1.8-1 (same version in Bookworm).
Anyway, after testing, I can't reproduce the problem on a generic cloud-init image, so that can maybe help?
Here is my test setup:
- Ubuntu 22.04 KVM/Qemu started from generic cloud-init images (amd64);
- kernel upgraded to 6.5.0-1015-azure;
- podman/crun installed from ubuntu repos.
Following command works: fauust/ docker- systemd: debian- 11
$ podman run --rm -d ghcr.io/