-
Notifications
You must be signed in to change notification settings - Fork 83
Use centos7 VirtualBox image from Atlas #17
Comments
If the plugin is missing, the error message is unreadable. But there's the possibility to check for installed plugins and bail out with a telling error. This will allow a smooth change for users. |
Take @lazyfrosch 's shell_provisionier. https://github.com/Icinga/icinga-build-vagrant/blob/master/scripts/shell_provisioner.sh Also kill the finialize script and do that inline based on #53 |
Boxes:
|
Refactor Vagrantfile, use centos/7 box for VirtualBox, require vbguest plugin Many thanks to @lbetz & @lazyfrosch for the inspirations! fixes #17 fixes #53
I'm really unhappy with the current state and fiddling with the additional vbguest module. I'd prefer a centos base image which already includes the virtualbox guest tools. This must also work flawlessly on Windows, since the boxes serve as local demo too. See CentOS/sig-cloud-instance-build#27 @bobapple is it safe to assume that http://boxes.icinga.com/vagrant/centos/centos-7.3-x64-virtualbox.box is available for the time being? |
I'll stick with https://atlas.hashicorp.com/bento/boxes/centos-7.3 as this is recommended by many. |
Explicitly disable SELinux. refs #17
Done, all tests were fine. |
This requires us to
Ensure that these changes work with Parallels and libvirt as provider.
Edit: There are certain problems with the official centos/7 box as it does not provide the VirtualBox guest tools. The
vagrant-vbguest
plugin would solve this somehow, but adds a dependency for the end user to install. Furthermore there are known bugs with VirtualBox guest additionals (5.1.20 is broken atm). I cannot support such scenarios and therefore need a box with has the guest additions pre-installed.Final solution: Use the boxes provided by bento and clearly note that in the docs.
The text was updated successfully, but these errors were encountered: