-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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. #6194
Comments
This is likely related to issue #6026, probably want to keep track of that. |
Try running command with --provider virtual, it worked for me. |
Worked for me! |
using --provider virtualbox worked for me. |
Hi all, Thank you for opening an issue. I believe this is occurring because of an issue in the laravel/homestead box and not Vagrant. That being said, I tried a few Vagrant boxes here locally (including the latest laravel/homestead), and none of them exhibited this issue. I am going to close this issue, since the problem appears to be fixed. The other thing you can try (if using git bash) is to tell Vagrant you are using cwgwin:
|
@sethvargo the export solved this issue for me. |
@sethvargo thanks man it worked for me |
When i go to my project ..for example - /cygdrive/c/project/HoXXey/Project-tt and do a vagrant destroy .it is throwing Error Vagrant is attempting to interface with the UI in a way that requires How to solve this issue |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Occuring this problem while adding vagrant box to laravel/Homestead in git bash => "vagrant box add laravel/homestead"
The text was updated successfully, but these errors were encountered: