Description:
Creating a new Ubuntu container as per the instructions at https://wiki.archlinux.org/title/systemd-nspawn#Create_a_Debian_or_Ubuntu_environment does not allow the created container to have the `machinectl shell root@vm-focal /bin/bash` command run. Previously this has worked.

The container can be ran via `systemd-nspawn` without the `-b` option and seems intact and usable.

However any command run via `machinectl shell` for a running container causes a coredump - even simple ones like `ls`

Only an Ubuntu container seems to do this - an equivalently made arch container runs just fine. I have not tried Debian.
Checking the upstream systemd repo is not showing anything like this at the moment.

Additional info:
* systemd 250.2-2
* linux 5.16.arch1-1
* Systemd cat for the `systemd-nspawn@vm-ubuntu.service`
* Journal output for the `systemd-nspawn@vm-ubuntu.service`
* `SYSTEMD_LOG_LEVEL=debug machinectl shell vm-focal /bin/ls` output

Steps to reproduce:
* Create a container with a bootable ubuntu systemd `debootstrap --include=systemd-container --components=main,universe focal /var/lib/machines/vm-focal http://archive.ubuntu.com/ubuntu/`
* Set the password for root
```
systemd-nspawn -D /var/lib/machines/vm-focal
passwd
exit
```
* Start the container `machinectl start vm-focal`
* Attempt a trivial shell call ie: `machinectl shell vm-focal /bin/true`