The name of the vagrant machine is default and provider is virtual box in this case. rw-r-r- 1 fhenri staff 63 Aug 28 22:18 vagrant_cwd rw-r-r- 1 fhenri staff 316 Sep 6 10:18 synced_folders rw- 1 fhenri staff 1679 Aug 28 22:18 private_key rw-r-r- 1 fhenri staff 32 Aug 28 22:18 index_uuid rw-r-r- 1 fhenri staff 3 Aug 28 22:18 creator_uid rw-r-r- 1 fhenri staff 148 Sep 6 09:42 box_meta rw-r-r- 1 fhenri staff 10 Aug 28 22:18 action_set_name rw-r-r- 1 fhenri staff 40 Aug 28 22:20 action_provision

vagrant/machines/default/virtualbox/ĭrwxr-xr-x 11 fhenri staff 352 Aug 28 22:20. The content of this folder has the Virtalbox vm informationįor example: ls -all. You can notice that we have added the config.vm.box_check_update = false in both web and app server provisioning segments.In your project directory (the one where you have the Vagrantfile) vagrant will create.

This Vagrant file created web server and application servers with two different boxes and two different configurations. The Sample Vagrantfile with this feature enabled. This can be controlled by your Vagrantfile The Fixīy default this update checking feature is enabled for all the new VMs being created with Vagrant unless you explicitly disable it by adding the following line into your vagrant fileĪfter adding this property in Vagrantfile, vagrant up command will not check for the new updates as it brings up the virtual machines

īy default when you bring up the virtual machine provisioned with vagrant using vagrant up command.vagrant will look for the updates associated with the box and make sure it is up to date. How to solve the situation where the vagrant up command gets stuck while checking if box is up to date.

Box vagrant