However, vagrant, as supplied as a package in the Ubuntu archive in Universe is not => 2.2.16 until Jammy. This means that host systems of 20.04, 18.04, and 16.04 using the universe packaged vagrant will be unable to start the Jammy image.
A workaround is stated in gh issue 11783: to provide our own newer key that matches the algorithms that the guest system expects, without needing the renegotiation fix put in place in vagrant.
currently published 22.04 Vagrant images will fail to finish booting on systems running vagrant < 2.2.16. The upstream issue is described here:
https:/ /github. com/hashicorp/ vagrant/ issues/ 11783
The fix in future vagrant versions is committed here:
https:/ /github. com/hashicorp/ vagrant/ pull/12298
However, vagrant, as supplied as a package in the Ubuntu archive in Universe is not => 2.2.16 until Jammy. This means that host systems of 20.04, 18.04, and 16.04 using the universe packaged vagrant will be unable to start the Jammy image.
A workaround is stated in gh issue 11783: to provide our own newer key that matches the algorithms that the guest system expects, without needing the renegotiation fix put in place in vagrant.