Tests no longer run on systemd > 248

[basil]

Jenkins and plugins versions report

Jenkins 2.379

What Operating System are you using (both controller, and any agents involved in the problem)?

Ubuntu 22.04.1 LTS x86_64
systemd 249 (249.11-0ubuntu3.6)

Reproduction steps

$ docker-compose run --rm packaging bash
$ ./prep.sh
$ make package
$ exit
$ python3 -m venv venv
$ . venv/bin/activate
$ pip install -r requirements.txt
$ molecule test

Expected Results

The tests pass. They actually do pass in the CI build (which must be using a VM with systemd 248 or earlier) and used to pass on my local machine a few months ago, but no longer pass on my local machine in recent weeks after I have upgraded the packages in my local Ubuntu installation to systemd 249.

Actual Results

The tests fail to run systemctl daemon-reload. dmesg(1) reports:

[  977.256889] systemd[1]: Set hostname to <debian-11>.
[  977.258394] systemd[1]: Failed to create /init.scope control group: Read-only file system
[  977.258625] systemd[1]: Failed to allocate manager object: Read-only file system
[  977.258661] systemd[1]: Freezing execution.

Anything else?

systemd/systemd#19245 and moby/moby#42275 go into the gory details. Apparently this was never "supported" to begin with, and the "official" way to do this is to use Podman instead as in gjhenrique/rpi_stuff@10cf31f, though this would likely require some additional work to get Podman set up in the VM image for the CI build. johanssone/ansible-unbound@ec3cbb8 shows a way to do this with Docker and systemd > 248, but this might break the CI build unless the VM image for the CI build is also updated to systemd > 248 in lockstep. In other words I suspect that any solution to this problem involves working on the VM image used for the CI build.