Hi everyone,
I'm pleased to announce the release of Vagrant 1.9.7. This is a small
release mostly focused on resolving a few platform related issues targeted
at MacOS and Windows. The vagrant ssh command has been fixed on Windows
when running within Cygwin or Msys environments. On MacOS the
I have a directory that sometimes is used in a native environment on bare
metal and other times used in a VM started with vagrant up. The only
difference is a few config files. What is the accepted way of getting the
VM version of the config files in place when a vagrant up is run?
I tried
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
Hello all,
I created my own box, and the box, and the Vagrantfile included in the box
has the following content:
Vagrant.configure("2") do |config|
config.vm.provider :libvirt do |libvirt|
libvirt.disk_bus = 'virtio'
end
config.vm.synced_folder ".",
Hello
Vagrant does stuff on your behalf.
It create the VM, it create the shared folder. up to there, Vagrant did his
job.
What I am saying is:
- Shared folders over virtualbox is not a native filesystem.
say you want XFS, the way to go is create a disk on the VM, put a XFS
filesystem and use
