From 2c67743f07890b31f8b9a0ac8fae63485c50d2cc Mon Sep 17 00:00:00 2001 From: Darragh Bailey Date: Wed, 5 Oct 2022 00:56:31 +0100 Subject: [PATCH] Note that vagrant may select nfs or rsync as default synced_folder (#1630) Depending on the installed packages present on the host system, vagrant may select either nfs or rsync as the default synced_folder implementation. Fixes: #419 --- docs/examples.markdown | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/examples.markdown b/docs/examples.markdown index 668f629..00713cd 100644 --- a/docs/examples.markdown +++ b/docs/examples.markdown @@ -191,20 +191,25 @@ collisions for multi machine environments gracefully. Vagrant automatically syncs the project folder on the host to `/vagrant` in the guest. You can also configure additional synced folders. +If the type is not specified, vagrant will attempt to select one based on the +highest priority that is usable. This can mean that depending on whether you have +the packages installed to support nfs and or rsync, you may experience different +behaviour on different machines. Recommendation is to be explicit. + **SECURITY NOTE:** for remote Libvirt, nfs synced folders requires a bridged public network interface and you must connect to Libvirt via ssh. **NFS** `vagrant-libvirt` supports -[NFS](https://www.vagrantup.com/docs/synced-folders/nfs) as default with +[NFS](https://www.vagrantup.com/docs/synced-folders/nfs) as with bidirectional synced folders. Example with NFS: ``` ruby Vagrant.configure("2") do |config| - config.vm.synced_folder "./", "/vagrant" + config.vm.synced_folder "./", "/vagrant", type: "nfs" end ```