x64 Windows 10 Pro VirtualBox v5.1.30 Vagrant v2.0.0 Vagrant is FUBAR Apparently I made the mistake of updating ubuntu/trusty64 that is pushing Vagrant around like a bully.
Now Vagrant will not halt or delete or much of anything else as there is some conflict with stdin is not a tty I've scowered the www and there are scant solutions. One of which is already written into the Vagrant file which I have no idea how it got there but it does not prevent stdin is not a tty either. I know its not a Vagrant error but there should be a reliable way to resolve this matter and IMO it should come from Hashicorp as they and they alone know Vagrant inside and out and how Vagrant interacts with boxes such as ubuntu/trusty64. That said if Hashicorp continues to ignore this matter then what? -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2f6f117b-da46-4550-8e1d-661b7bbd007d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
