CODEWITHSUNDEEP
interfacevagranttty
sl5
sl5

Reputation: 191

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

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 ).

how can it be fixed?

    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

thanks

Upvotes: 19

Views: 17161

Answers (8)

Zwadderich
Zwadderich

Reputation: 251

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

vagrant destroy m001 -f

This is happening because when script attempts vagrant destroy, Vagrant asks for [Yes/No] confirmation. Adding -f skips that.

Upvotes: 15

Heto
Heto

Reputation: 595

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

Upvotes: 0

aldrien.h
aldrien.h

Reputation: 3635

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.

Upvotes: 2

chrki
chrki

Reputation: 6333

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.

Upvotes: 2

user151841
user151841

Reputation: 18046

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.

Upvotes: 21

Mihai MATEI
Mihai MATEI

Reputation: 506

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.

Upvotes: 0

phpPhil
phpPhil

Reputation: 926

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

Upvotes: 5

Al Belsky
Al Belsky

Reputation: 1592

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.

Upvotes: 14

Related Questions