Re: Fw: Vagrantfile's config.vm.some-key is breaking vagrant-up in vbox 4.3
Thanks M. Kasper! That is useful.
I wonder if it could be wrapped somehow so it does not break usage under older versions of vagrant.
And if a base box is only going to work with certain versions of vagrant, that would be a useful warning.
Its not virtualbox, but vagrant which needs to be upgraded.
Can you go upstream to source for that, please?
On Sat, 10 Feb 2018 11:12:52 +0100
Emmanuel Kasper <firstname.lastname@example.org> wrote:
> Le 10/02/2018 à 00:44, Kevin Hatfield a écrit :
> > `config.vm.post_up_message` is offending parameter with virtualbox 4.3
> > "Bringing machine 'default' up with 'virtualbox' provider...
> > There are errors in the configuration of this machine. Please fix
> > the following errors and try again:
> > vm:
> > * The following settings shouldn't exist: post_up_message"
> Hi Kevin
> The post_up_message feature was added in Vagrant 1.6.
> Maybe you have an older Vagrant version ?
> This message is displayed by Vagrant itself and not Virtualbox, so I
> don't think the VirtualBox version you have does matter.
Hugh Esco <email@example.com>