since I’ve just hit this myself on ec2 earlier today, here’s a workaround incase anyone needs it until a fixed build is uploaded
systemd-ssh-generator(8)[0] documents parameters that can be set to steer this. I’ve tested this to work on ec2 example: ``` echo ‘GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX systemd.ssh_listen=22”’ >> /etc/default/grub update-grub ``` a subsequent reboot results in working ssh: > Aug 19 23:28:27 sshdebug systemd[1]: Listening on sshd-extra.socket - OpenSSH > Server Socket (systemd-ssh-generator, [::]:22). `systemd-ssh-generator` still fails on the vsock check as before, but ssh does appear to reliably persist working through both `systemctl daemon-reload` and a reboot -J [0] - https://manpages.debian.org/unstable/systemd/systemd-ssh-generator.8.en.html
