![vagrant cygwin installation vagrant cygwin installation](https://i.stack.imgur.com/mtGe1.png)
- #VAGRANT CYGWIN INSTALLATION INSTALL#
- #VAGRANT CYGWIN INSTALLATION UPDATE#
- #VAGRANT CYGWIN INSTALLATION CODE#
- #VAGRANT CYGWIN INSTALLATION DOWNLOAD#
$ vagrant box update -box nrgxnat/xnatstack-ubuntu1404-docker If you get an error because you already have a previous version of the xnatstack box installed, you can update it with the following command. $ vagrant box add nrgxnat/xnatstack-ubuntu1404-docker -provider virtualbox ( xnat-vagrant/configs/xnat is the default.) Then, you'll run the following command: /repos/xnat-vagrant/configs/xnat reposīefore You Run setup.sh 4: Make sure your vagrant xnatstack box is up-to-dateįirst, you'll need to navigate to one of the configuration directories in your newly-downloaded repo. The process should take just a few seconds. Open Cygwin and navigate to your repos directory, then run the following command. Setup.sh: line 36: syntax error: unexpected end of fileĬloning the xnat-vagrant repo with git is simple. Setup.sh: line 6: $'\r': command not found Setup.sh: line 4: $'\r': command not found Setup.sh: line 2: $'\r': command not found If you start seeing problems when running "setup.sh" that look like the following, then you need to convert the line endings of affected files ( Notepad++ can do this easily), or you can delete your repo and re-clone it (make sure you back up any local configuration files first). SourceTree can be particularly troublesome, as it comes with its own pre-downloaded and pre-configured version of Git, and its default configuration gets these line-endings wrong.
#VAGRANT CYGWIN INSTALLATION CODE#
This is particularly bad in code that is downloaded to a Windows machine, but is meant to be run inside of a Linux VM.
![vagrant cygwin installation vagrant cygwin installation](https://kizu514.com/blog/wp-content/uploads/2015/09/2-Add-CYGWIN-System-Variable.jpg)
If you would prefer to set this globally for all Git repos, during installation of Git, select the option to "Checkout as-is, commit Unix-style Line Endings."ĭownloading Git directly and using it to clone repos from Github will help you get around pernicious differences between Unix-style and Windows-style line-endings in code. There is a '.gitattributes' file included in the xnat-vagrant repo that should force UNIX line endings.
#VAGRANT CYGWIN INSTALLATION DOWNLOAD#
$ ln -s C:/path/to/your/Repos /reposīefore You Clone The xnat-vagrant Repo 3: Download Git and use it to clone the xnat-vagrant repository instead of SourceTree or any other GUI tools You can also create a shortcut within Cygwin to your Repos directory by entering something like the following, substituting your actual directory path for "/path/to/your/Repos". Enter the following to navigate to your C: drive. It is simple, if a bit unintuitive, to navigate out to your file system. When you run Cygwin, it creates a new (empty) home directory. This should ensure that all required packages (OpenSSH in particular) are included. The best way to do this is to select "Install From Internet" as your installation method, then select the topmost mirror () as your download source. Make sure your installer is set to pull down every available package. If you're using Cygwin, there are several dialogs that must be configured. If you want a more full-featured GUI wrapped around your command line app, you can use MobaXterm – however, there is a workaround in MobaXterm that must be followed to enable Vagrant to SSH into your VirtualBox VM.
#VAGRANT CYGWIN INSTALLATION INSTALL#
We recommend using Cygwin, which can be downloaded and installed as a stand-alone app, or Git Bash, which comes with Git (which you will need to install in just a moment here). Fortunately, there are third party command line tools that are free to use that do.
![vagrant cygwin installation vagrant cygwin installation](https://image.slidesharecdn.com/vagrant-140112033458-phpapp02/95/vagrant-22-638.jpg)
Make sure you are running your command line app (Cygwin, Git Bash, MobaXTerm etc) as an administrator! (See Sanket's comment thread below.)įor whatever reason, the default command line terminal in Windows does not play well with Vagrant and VirtualBox, even when run as an administrator.