-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Rsync Input Line is Too Long #5834
Comments
The Windows-to-Windows Rsync setup is just not working... I was amazed... I solved the "input line is too long" problem by moving my host's home for the Vagrant to c:\vagrant... which suggests that ultimately there is a limit for the rsync command length that is partially comprised of the path... and pretty much any path more than 1 folder deep is going to make the whole rsync command too long. That said, I got past the "input line too long" thing ... and got back into rsync details...
So then I looked at debug output for both a boot, and just using "vagrant rsync"... here is the boot debug output
And here is the output of "vagrant rsync" ...
|
Unfortunately I don't see a way to slve this since there is no way to specify the input paths without using the CLI. it seems that the CLI itself, the shell or rsync (I'm not sure which) is pretty broken. I'm not sure what Vagrant can do about that. I'm sorry but rsync will not work for you |
I think this bug has morphed. Indeed there is a bug with the path length in Windows - a bug that I can understand is not resolvable by Vagrant as the OS itself is limiting the parameters. But there is also a different issue where even if rSync is running when the paths involved do not exceed the required max length, it is still not working. I don't think they are the same issue. I'm going to continue investigating but may open a separate bug for that. |
@nfloersch I agree with that, please search first since I'm quite confident I saw other issues related to that. |
Getting an error when setting up an rsync'd folder between a Windows Vagrant host and a Windows Vagrant client. I have tried various Windows rsync options - cwrsync, rsync from git, and mingw, and now cygwin.
I'm using a VMWare Workstation provider (Workstation v11, pro).
Vagrant is v1.7.2
Windows 8.1 host
I've tried cwrsync, rsync, git, mingw, and cygwin packages from Chocolatey... in the cases where I got rsync to work at all, it always seems to come down to this same error:
---snip---
---snip---
I understand that there is no easy circumvention of the max length of characters in a CMD input... but then it seems impossible that this has ever worked for anyone... I'm not hiding my data in some strange, deeply nested path. I'm trying to sync c:\users\nick\vagrant\agbmp to c:\vagrant...
Ultimately, this is the last thing I can seem to try before ditching Vagrant - the sync'd folder thing in a Windows environment just seems to be completely unusable with NPM... which defies the purpose of using Vagrant for us. I've read that in some cases using the rsync'd folder with Vagrant works better because there are no cross-shared-folder symlinks. But honestly the rsync support in Vagrant still seems incredibly *nix oriented, as well.
The text was updated successfully, but these errors were encountered: