Re: [vagrant-up] config.vm.synced_folder ignored in default Vagrantfile

2017-07-17 Thread Alvaro Miranda Aguilera
hello can you check the file is there once untarred by Vagrant? find ~/.vagrant.d/boxes if you add puts __FILE__ it should print the name of the file when you run any command, ie vagrant status this is helpful to confirm is being loaded. if thats the case, then could you open an issue on git

Re: [vagrant-up] config.vm.synced_folder ignored in default Vagrantfile

2017-07-12 Thread Krist van Besien
I've been using Vagrant extensively. So I know the difference between init and up. My problem is the following: - I created a box myself, by packaging an image, together with a Vagrantfile and a Metadata.json file. - In that Vagrantfile I have the following content: Vagrant.configure("2") do |

Re: [vagrant-up] config.vm.synced_folder ignored in default Vagrantfile

2017-07-07 Thread Salty Vagrant
I suspect this is simply a misunderstanding of the vagrant commands. Once you have your edited Vagrantfile (with the synced_folder disabled) you should use ‘vagrant up’ NOT ‘vagrant init’. ‘vagrant init’ creates a new Vagrantfile and sets the vm/box to the value you provide on the command lin