Vagrant 试图以需要 TTY 的方式与 UI 交互 [英] Vagrant is attempting to interface with the UI in a way that requires a TTY

问题描述

问题:vagrant up 失败并出现以下错误.我在 Windows 7 上运行 vagrant，基本框是 Ubuntu )( files.vagrantup.com/precise32.box ).

Problem: vagrant up fails with the error below. I am running vagrant on Windows 7 and the base box is Ubuntu )( files.vagrantup.com/precise32.box ).

怎么解决?

    vagrant.bat up

Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Available bridged network interfaces:
1) Intel(R) PRO/1000 EB Network Connection with I/O Acceleration
2) Intel(R) PRO/1000 PL Network Connection
Vagrant is attempting to interface with the UI in a way that requires
a TTY. Most actions in Vagrant that require a TTY have configuration
switches to disable this requirement. Please do that or run Vagrant
with TTY.

Process finished with exit code 1

谢谢

推荐答案

This 在 cygwin 上为我工作:

This worked for me on cygwin:

或者将其添加到 ~/.bashrc:

Or add this to ~/.bashrc:

export VAGRANT_DETECTED_OS=cygwin

然后我收到Vagrant 显示一条消息，它需要运行一些内部升级......"

Then I got the "Vagrant displays a message that it needs to run some internal upgrades..."

编辑 - 糟糕！很快就讲到了.在其更新期间，我收到 Warning: Authentication failure.重试... 直到超时:P

Edit - Oops! Spoke to soon. During its updates, I got Warning: Authentication failure. Retrying... until timeout :P

编辑 2 - 我能够修复它 通过将 config.ssh.private_key_path 设置为我的 Windows 用户主目录中的 .vagrant.d/insecure_private_key.

Edit 2 - I was able to fix it by setting config.ssh.private_key_path to the .vagrant.d/insecure_private_key in my Windows user's home directory.

这篇关于Vagrant 试图以需要 TTY 的方式与 UI 交互的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！