I recently upgraded to Virtulbox 6.0 and ever since I have not been able to get guest additions to work. This will assist us in providing a timely response and fix.Ubuntu 1604 -18.zip (34.54 KiB) Downloaded 12 timesI have had a stable Ubuntu 16.04 guest for several years (Win 7 host). If you do continue to encounter errors, please open a new issue and follow the issue template that appears. I'm doing this because I don't want this issue to become a black hole of "me too" and potentially mask real bugs. It's my least favorite thing to do, but I'm going to lock this issue. Unlike the "ubuntu" boxes, the bento boxes also support more providers such as VMware, Virtualbox, and Parallels. The bento boxes are open source and they are built using best practices and Packer. You can open bugs on launchpad, but I would highly recommend trying the bento boxes instead. Just as GitHub's support team is unable to assist with issues in someone's repository, HashiCorp's is not able to assist with third-party published boxes. Namespaces on Atlas behave very similarly to namespaces on GitHub, for example. A common misconception is that a namespace like "ubuntu" represents the canonical space for Ubuntu boxes. In general, users have had more success with the boxes under the bento namespaces. There are bare minimum requirements for building base boxes with Vagrant, and that image is simply malformed. None of these are bugs in Vagrant, and, unfortunately there is not very much Vagrant can do to make this experience better. They do not follow the recommended guides for how to build a Vagrant box, and they are missing key components such as guest additions, required packages, or they do things like hardcode the hostname to make running concurrent VMs impossible. As I said to on Twitter, the boxes published by canonical under the ubuntu namespace for 16.04 are very broken.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |