vagrant up fails (Windows 7 + PowerShell)

[spikecurtis]

Hi,

I'm having issues just getting the vagrant VMs to boot. Any idea what's up?

PS C:\Users\SJC\repos\powerstrip-flocker\vagrant> vagrant up
Bringing machine 'node1' up with 'virtualbox' provider...
Bringing machine 'node2' up with 'virtualbox' provider...
==> node1: Importing base box 'vagrant-powerstrip-flocker-demo-pulled-images'...
==> node1: Matching MAC address for NAT networking...
==> node1: Setting the name of the VM: vagrant_node1_1426633178937_82873
==> node1: Fixed port collision for 22 => 2222. Now on port 2200.
==> node1: Clearing any previously set network interfaces...
==> node1: Preparing network interfaces based on configuration...
    node1: Adapter 1: nat
    node1: Adapter 2: hostonly
==> node1: Forwarding ports...
    node1: 22 => 2200 (adapter 1)
==> node1: Booting VM...
==> node1: Waiting for machine to boot. This may take a few minutes...
    node1: SSH address: 127.0.0.1:2200
    node1: SSH username: vagrant
    node1: SSH auth method: private key
    node1: Warning: Connection timeout. Retrying...
    node1: Warning: Remote connection disconnect. Retrying...
    node1: Warning: Remote connection disconnect. Retrying...
    node1: Warning: Remote connection disconnect. Retrying...
==> node1: Machine booted and ready!
==> node1: Checking for guest additions in VM...
==> node1: Setting hostname...
==> node1: Configuring and enabling network interfaces...
==> node1: Mounting shared folders...
    node1: /vagrant => C:/Users/SJC/repos/powerstrip-flocker/vagrant
==> node1: Running provisioner: shell...
    node1: Running: inline script
==> node1: /vagrant/install.sh: line 2: $'\r': command not found
==> node1: /vagrant/install.sh: line 4: $'\r': command not found
==> node1: /vagrant/install.sh: line 8: $'\r': command not found
==> node1: /vagrant/install.sh: line 11: syntax error near unexpected token `$'{\r''
'=> node1: /vagrant/install.sh: line 11: `cmd-copy-vagrant-dir() {
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[binocarlos]

Hey - this looks odd - the only thing I can spot obviously is that it has \r as the line ending - is there a way to check if this file is using unix or windows line endings?

[binocarlos]

What I meant to say is to ask is git somehow checking out windows line endings