Comment 0 for bug 1969664
Revision history for this message
| John Chittum (jchittum) wrote 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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:/
The fix in future vagrant versions is committed here:
https:/
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.