I'm afraid so. I'm also using vagrant-berkshelf, which triggers the default folder sync/sharing action, causing SMB sharing to kick in.
David On Fri, Feb 13, 2015 at 12:40 AM, Alvaro Miranda Aguilera <[email protected] > wrote: > have you tried: > > config.vm.synced_folder ".", "/vagrant", disabled: true > > config.vm.synced_folder ".", "/vagrant", type: "smb", disabled: true > > On Fri, Feb 13, 2015 at 3:55 PM, David Severski <[email protected]> > wrote: > > Bumping this thread. The default behavior of Vagrant 1.7.2 to create SMB > > shares for every vagrant up action is not just annoying, but flat out > > non-functional. I don't understand how this can be a functional state for > > anyone running Vagrant on Windows hosts. Running with a non-admin command > > window isn't a good solution as I run both VMWare and AWS providers, so > > admin privs are needed for VMWare function. How can the behavior of using > > Windows SMB shares be fully turned off? > > > > Thanks for the help! > > > > David > > > > On Friday, January 16, 2015 at 7:59:48 AM UTC-8, David Severski wrote: > >> > >> Recent versions of Vagrant now default to creating shares on Windows > hosts > >> for mapping to guests. This is documented as an early iteration of the > >> feature and has some known problems, mainly with shares never being > cleaned > >> up across multiple different vagrant runs. I can't get this feature to > work > >> at all and would like to tell Vagrant to not use this method under any > >> circumstances. Setting a share stanza to disabled status is not > sufficient > >> as plugins such as vagrant-berkshelf will still try to create a share > and > >> map it with SMB. I can't easily run without admin privileges (the other > way > >> to avoid SMB from kicking in) as I use frequently use > >> vagrant-vmware-workstation which requires admin privs. > >> > >> How can I fully disable this interesting, but not yet ready for prime > >> time, feature of Vagrant 1.7.2 under Windows 7 x64? > >> > >> David > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Vagrant" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Vagrant" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vagrant-up/NwyTea-g6Vc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
