You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon rebooting the VM to re-set the hostname, I got this message:
[vagrant-images] $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'generic/freebsd11' is up to date...
==> default: A newer version of the box 'generic/freebsd11' for provider 'virtualbox' is
==> default: available! You currently have version '1.5.0'. The latest is version
==> default: '1.6.0'. Run `vagrant box update` to update.
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
Indeed, I get this message whenever I say vagrant update or vagrant provision anywhere on the host when I'm using the 'generic/freebsd11' box.
I'm reluctant to say vagrant box update until I understand the implications of that for all the libraries I've already installed inside the VM.
The text was updated successfully, but these errors were encountered:
@andrewvillano , On July 1 you wrote in email, "I ran vagrant update and it did not appear to have any negative impact on the VMs." I'm wondering: Did you run vagrant update or vagrant box update. (It was the latter that I was concerned about.)
Upon rebooting the VM to re-set the hostname, I got this message:
Indeed, I get this message whenever I say
vagrant update
orvagrant provision
anywhere on the host when I'm using the 'generic/freebsd11' box.I'm reluctant to say
vagrant box update
until I understand the implications of that for all the libraries I've already installed inside the VM.The text was updated successfully, but these errors were encountered: