-
Notifications
You must be signed in to change notification settings - Fork 573
Being asked for details for SMB instead of RSYNC #365
Comments
Oh, how I loathe the Vagrant SMB sharing feature. :( The workaround for this is to not run your command prompt with admin privileges. Using current vagrant and vagrant-aws with a regular user shell allows me to launch without the SMB sharing code (which never works for me) from firing. |
Is there a way to force a different sync mechanism? It looks like even if I set the sync option to "rsync", "smb" is still used when it comes to running the provisioner (I have chef solo configurations). |
Not that I've found so far. |
@michaelzhou999 still an issue? |
@bheuvel That works for the vagrant shared folders, but chef shared folders will still try to use SMB. 😢 |
For chef syncedfolders I think it would be like:
(Hope it helps. I'm not using aws plugin, but this works for me for the cloudstack plugin using (forcing to) winrm.) |
How about:
|
Adding the below command worked for me.
|
@bheuvel This helped me. Thank you sir. |
@bheuvel Worked for me. Thank you. |
@hemags worked for me as well |
On Vagrant >= 2.0 the sync folder type by default is SMB on macOS, so we need to force it to use rsync. Refs: puphpet#2764 hashicorp/vagrant#9960 mitchellh/vagrant-aws#365 devopsgroup-io/vagrant-digitalocean#277
Probably overkill but basically implemented everything from mitchellh/vagrant-aws#365
* Fix SMB username prompt: mitchellh/vagrant-aws#365 * Update versions * Remove legacy database cookbook attributes
This worked for me! I haven't run a vagrant up using vagrant-aws for about 5 months and I go t the "SMB" prompt. This fixed it. Thanks. |
Hey there.
Host: Windows 7
I am being asked for details for SMB instead of RSYNC when using vagrant-aws. Is there any way to force RSYNC? Or am I doing something completely wrong?
VagrantFile:
Output:
Thanks!
The text was updated successfully, but these errors were encountered: