Vagrant is attempting to interface with the UI in a way that requires a TTY

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-29 03:07:00

This worked for me on cygwin:

Or add this to ~/.bashrc:

export VAGRANT_DETECTED_OS=cygwin

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

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

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.

I got the same error after upgrading Vagrant from 1.4 to 1.6.3 (Windows 7).

Running VAGRANT_HOME\bin\vagrant.exe manually resolved this issue for me:

  • Execute VAGRANT_HOME\bin\vagrant.exe
  • Vagrant displays a message that it needs to run some internal upgrades
  • "Press any key to continue"...
  • Once the process finished (it took several minutes), I was able to proceed with Vagrant instance launch as usual.

i had the same error while destroying a machine. I simply added -f and it did the job.

vagrant destroy m001 -f

This is caused by Vagrant finding multiple Ethernet interfaces that can be used as public network and Vagrant cannot decide which one to use.

There are 3 options:

  1. Deactivate one of the 2 adapters, so that Vagrant can use the other

  2. Specify the Ethernet adapter you would like Vagrant to use in the vagrantfile. Like this:

    app.vm.network "public_network", bridge: "Intel(R) PRO/1000 PL Network Connection"
    
  3. Running the vagrant executable manually as already described in Al Belsky's answer

If you are on Windows and are starting Vagrant through MinGW (Git Bash for example) and get this message, try running it once through Windows' default cmd.exe. You are then able to answer the question about your network adapters.

I'm using Vagrant 1.7.4

Execute the below code before running vagrant up:

export VAGRANT_DETECTED_OS=cygwin

That will eliminate the exiting of vagrant and will allow you to choose Network Interface.

This may also be caused by not having Hardware Virtualization enabled in BIOS.

Also encountered this with Windows 10, when Vagrant cannot properly detect OS.

also can happen if you have both vmware and virtual box installed and you try to use MinGW.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!