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

查看:252
本文介绍了Vagrant正试图以需要TTY的方式与UI进行交互的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

问题: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

谢谢

推荐答案

这对我在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..."

编辑 - 哎呀!很快就说。在更新期间,我得到警告:身份验证失败。重试... 直到超时: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屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆