Hi all, I was able to use the `ssh` command from my $PATH as follows.
ssh [email protected] -p2222 -i C:/users/sdalziel/learn-chef/.vagrant/machines/default/virtualbox/private_key I feel that this is only a work-around and hope to either post or see the steps to repair soon. Cheers. S On Sunday, 17 December 2017 12:57:34 UTC-5, Robert Lilly wrote: > > I too am experiencing this, same setup. I am suspecting something with the > latest version of Git for Windows. When I use cmd.exe to do 'vagrant up' > and then 'vagrant ssh' I get the normal BASH prompt and things look as > expected. But when I use Git Bash, after doing 'vagrant ssh' things get > wonky. Also, if I launch the VirtualBox GUI and access the VM that way I > get a normal BASH prompt. > > I will try rolling back to an earlier version of Git for Windows and see > how that works. I will report my findings back here. > -- 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/943507be-1b91-4ab9-8d24-39b72e85ac39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
