I have a computer that runs Windows 8.1 and for some projects I use Vagrnat and VirtualBox, however after upgrading VirtualBox and Vagrant, after running Vagrant ssh, vagrant doesn't display the command prompt. I thought that may be it's a problem related with old boxes so I've create a new VM but the results is the same.

As you can be seen below, some commands return results and everything is fine

sudo -i returns me that stdin: is not a tty

Could you have a look please and give me an idea about how can I solve this problem?

  • 1
    Not familiar with Vagrant, but if you usually do something like ssh vagrant@ does it work better if you ssh -t vagrant@ or even ssh -tt vagrant@ – roaima Jul 13 '17 at 14:53

I have the same problem on Windows 10 Home 64bit with Creators Update, Vagrant 1.9.6, VirtualBox 5.1.22r115126 and Cygwin. Following https://github.com/mitchellh/vagrant/issues I read that this can happen with cygwin/babun/gitbash but not with the cmd-prompt.

So I booted another box with the Windows cmd-prompt and yes, I can confirm that after vagrant up and vagrant ssh you are getting the prompt inside your box. Not ideal but workable for the time being.

Not sure what is causing this though, as I didn't update cygwin for a long time, and it had been working with Vagrant 1.9.6 .

Instead of using the Windows cmd-prompt, updating to Vagrant 1.9.7 also fixes this issue, at least for me :)

  • I am using vagrant 2.0.1 and I still have this issue with Cygwin or GitBash. I can confirm that it works fine in PowerShell. – Johnny Jan 12 '18 at 17:28
  • I was worked in v2.0.0 and now is broken in v2.1.2 – gavenkoa Jul 3 '18 at 12:58

I'm running a Windows 10 development environment (cygwin/babun + mintty) and had the same issue after upgrading Vagrant. While I haven't found a solution to the problem using vagrant ssh, I did find a workaround.

Turns out, I'm able to ssh into the virtual environments normally. Look at the assigned IP address in your Vagrantfile, say, If you use the command:

ssh vagrant@

you should be able to enter the password "vagrant" (standard for vagrant boxes) and use the machines normally. It is my understanding that this has something to do with passing along TTY interface to the terminal window. Prior versions of "vagrant ssh" used the ssh that was in the host's path, but looks like the newer versions have a version of ssh embedded that doesn't play nicely with Windows environments (this is from my limited experience and research yesterday).

If you want to access without using a username/password combination, there is a quick workaround there as well. I created the following function in my .babunrc file, though I imagine any .bashrc or .bash_profile would work:

# Vagrant ssh-config to file
function devConfig () {
    vagrant ssh-config > "PATH TO YOUR SSH CONFIG FILE"

This allows you to reconfigure your config each time you roll over your Vagrant boxes. Note that this will overwrite any config you currently have setup. You can switch to appending by using ">>", however you'll end up with a huge config file if your rolling your development environments frequently. Obviously that's not a solution that works for everyone.

Regardless, it's super curious that the newer versions have bundled this ssh package that can't pass along TTY. I'm not a strong enough user to understand why, but at least the problem can be identified.

  • VAGRANT_PREFER_SYSTEM_BIN=1 or 0 controls which ssh client to use with at least v2.1.2 – gavenkoa Jul 3 '18 at 13:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.