Yeah. i want to compare the bootstrap/install.sh and other files as well 
under bootstrap.
but this command ie dos2unix  needs to used on windows right. and for that 
i need to install this also. how to do that in windows. i checked online 
and it shows only for Liinux

On Tuesday, 24 December 2019 15:27:10 UTC+5:30, Alvaro Miranda Aguilera 
wrote:
>
> Hello
>
> You can learn more here:
>
>
> https://unix.stackexchange.com/questions/32001/what-is-m-and-how-do-i-get-rid-of-it
>
>
> basically there are characters in the script you are trying to run, that 
> in the VM are causing issues
>
> bootstrap/install.sh
>
>
> alvaro
>
>
> On Tue, Dec 24, 2019 at 10:48 AM Ravjot Singh <[email protected] 
> <javascript:>> wrote:
>
>> I am not aware what are you saying.? dos2unix needs to be installed on 
>> windows right and which file to compare with this tool? and will this help?
>>
>>
>>
>> On Tuesday, 24 December 2019 15:10:48 UTC+5:30, Alvaro Miranda Aguilera 
>> wrote:
>>>
>>> hello
>>>
>>> this error
>>>
>>> ^M: bad interpreter:
>>>
>>> is cause when you edit files on windows and then run in linux, end of 
>>> line is different between the OS
>>>
>>> you will have to remove the end of line that are causing this, you can 
>>> try using a tool called dos2unix
>>>
>>> alvaro.
>>>
>>>
>>>
>>> On Tue, Dec 24, 2019 at 9:13 AM Ravjot Singh <[email protected]> wrote:
>>>
>>>> Please help on this.. When i run Vagrant up, i get the below error.
>>>> Attaching the full logs as under :
>>>> I did a vagrant reload to halt and start again and as it asked me to 
>>>> provision, so i ran the command vagrant provision. 
>>>>
>>>> Any idea guys am i doing it correct???
>>>>
>>>>
>>>> C:\BlockChain\devbox>*vagrant reload*
>>>>
>>>> ==> default: Attempting graceful shutdown of VM...
>>>> ==> default: Checking if box 'ubuntu/xenial64' version '20191211.0.0' 
>>>> is up to date...
>>>> ==> default: Clearing any previously set forwarded ports...
>>>> ==> default: Clearing any previously set network interfaces...
>>>> ==> default: Preparing network interfaces based on configuration...
>>>>     default: Adapter 1: nat
>>>> ==> default: Forwarding ports...
>>>>     default: 8080 (guest) => 8080 (host) (adapter 1)
>>>>     default: 4000 (guest) => 4000 (host) (adapter 1)
>>>>     default: 22 (guest) => 2222 (host) (adapter 1)
>>>> ==> default: Running 'pre-boot' VM customizations...
>>>> ==> default: Booting VM...
>>>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>>>     default: SSH address: 127.0.0.1:2222
>>>>     default: SSH username: vagrant
>>>>     default: SSH auth method: private key
>>>> ==> default: Machine booted and ready!
>>>> [default] GuestAdditions 6.0.14 running --- OK.
>>>> ==> default: Checking for guest additions in VM...
>>>> ==> default: Mounting shared folders...
>>>>     default: /vagrant => C:/BlockChain/devbox
>>>>     default: /home/vagrant/bootstrap => C:/BlockChain/devbox/bootstrap
>>>> ==> default: Machine already provisioned. Run `vagrant provision` or 
>>>> use the `--provision`
>>>> ==> default: flag to force provisioning. Provisioners marked to run 
>>>> always will still run.
>>>>
>>>> C:\BlockChain\devbox>*vagrant provision*
>>>> ==> default: Running provisioner: shell...
>>>>     default: Running: inline script
>>>>     default: /tmp/vagrant-shell: /home/vagrant/bootstrap/install.sh: 
>>>> /bin/bash^M: bad interpreter: No such file or directory
>>>> 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.
>>>>
>>>> -- 
>>>> This mailing list is governed under the HashiCorp Community Guidelines 
>>>> - https://www.hashicorp.com/community-guidelines.html. Behavior in 
>>>> violation of those guidelines may result in your removal from this mailing 
>>>> list.
>>>>  
>>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>>> IRC: #vagrant on Freenode
>>>> --- 
>>>> 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].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/vagrant-up/392f8fe4-2db6-45dc-af44-af73a8d89cab%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/vagrant-up/392f8fe4-2db6-45dc-af44-af73a8d89cab%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Alvaro
>>>
>>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> 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] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/3e689c88-c42e-4aa5-af44-b4b39d40b4da%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/3e689c88-c42e-4aa5-af44-b4b39d40b4da%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/463f3bac-2b2b-4aea-b408-22ab7a2a91fb%40googlegroups.com.

Reply via email to