VirtualBox 6 and Vagrant 2.2.3 compatibility

[grant-veepshosting]

Cannot get this demo to run on the current version of Virtualbox and Vagrant.

[petems]

Ok, when you run vagrant up, what errors do you see? And what issues are you having with the Vault steps?

[grant-veepshosting]

Vagrant up errors but seems to complete on the 2nd run, with no sign of the designated IP address. This could be related to the baked in VM tools not working and subsequently the mapped folders not passing through. I hacked around to get latest VM tools working and re-provisioned in vagrant, resulting in a 2nd network interface with the designated address. After remapping the shared folder, I got a puppet master to fire correctly, and all clients came up and had certificates signed, but would not retrieve the correct catalogues for their assigned roles..

…

On Wed, Feb 6, 2019, 9:11 PM Peter Souter ***@***.*** wrote: Ok, when you run vagrant up, what errors do you see? And what issues are you having with the Vault steps? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ApCK8NRkk6PJn1nMn0EGc1cdXa_fCShIks5vKqpOgaJpZM4akkBB> .

[petems]

Can you try installing https://github.com/dotless-de/vagrant-vbguest?

vagrant plugin install vagrant-vbguest

This should fix the folder syncing issues on Virtualbox

[grant-veepshosting]

I've tried this combo on a different machine and a fresh clone: Vagrant 2.2.3, VirtualBox 5.2.26 & the recommended plugin. The Vagrant defined IP (also in the HOSTS files and Puppet manifests) is not added to the 2nd NIC, and the mapped folders are not present although it's not complaining about the virtual tools integration on this one.

…

On Thu, 7 Feb 2019 at 00:44, Peter Souter ***@***.***> wrote: Can you try installing https://github.com/dotless-de/vagrant-vbguest? vagrant plugin install vagrant-vbguest This should fix the folder syncing issues on Virtualbox — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ApCK8P75MyuzFm2-p2L-UoUBjlDy7ms1ks5vKtwngaJpZM4akkBB> .

[petems]

Ok, can you try removing the code that hard-codes the networks?

Then install this: https://github.com/oscar-stack/vagrant-hosts

And see if that helps?