-
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
Y/N prompt vagrant destroy does not work on Win 10 PowerShell #7649
Comments
@ColumbiaBlooms I have a feeling there is something within your Vagrantfile that is getting processed and looking for input that is causing the issue with not being able to destroy. Can you try commenting out most of the Vagrantfile except the boxname and see if you are then able to destroy? Also make sure if you have a Vagrantfile in Also, if you do a |
Before changing Vagrantfile "vagrant destroy --debug" results in a prompt, but when I type anything nothing happens. The keyboard input is ignore as if the process is hung. I have to stop the Ruby process. Here are the last few lines of output. DEBUG subprocess: Exit status: 0 Running "vagrant destroy -f" works just fine since there is no "y/n" prompt. I get the following errors when I type "vagrant destroy" with the new Vagrantfile. vagrant : Vagrant failed to initialize at a very early stage:
There was an error loading a Vagrantfile. The file being loaded Here is what's left of my Vagrantfile. I guess I didn't understand what you meant by leaving the boxname only. -- mode: ruby --vi: set ft=ruby :Vagrant box.config.vm.box = vconfig['vagrant_box'] VirtualBox.config.vm.provider :virtualbox do |v| |
You did good, just need to add this line back at the beginning of your file.
And another |
Getting the following messages with updates to Vagrantfile. vagrant : C:/Users/samst/Desktop/Drupal/DrupalVM/Vagrantfile:5:in
Current Vagrantfile. -- mode: ruby --vi: set ft=ruby :Vagrant.configure(2) do |config| Vagrant box.config.vm.box = vconfig['vagrant_box'] VirtualBox.config.vm.provider :virtualbox do |v| |
OK, can you look in the |
Still getting a syntax error. I guess I don't understand your instructions ... vagrant : There is a syntax error in the following Vagrantfile. The syntax
message is reproduced below for convenience: Vagrantfile contents: -- mode: ruby --vi: set ft=ruby :Vagrant.configure(2) do |config| Vagrant box.config.vm.box = <'geerlingguy/ubuntu1604'> VirtualBox.config.vm.provider :virtualbox do |v| |
I should have noted that you don't need the angle brackets, they were there On Aug 10, 2016 3:26 PM, "Sam Stamport" notifications@github.com wrote:
|
Still not working. I get the following when I type vagrant status. vagrant : There was an error loading a Vagrantfile. The file being loaded At line:1 char:1
and the error message are shown below. This is usually caused by a syntax error. Path: Line number: /Users/samst/Desktop/Drupal/DrupalVM/Vagrantfile Message: NameError: undefined local variable or method `vconfig' for main:Object Vagrantfile contents -- mode: ruby --vi: set ft=ruby :Vagrant.configure(2) do |config| Vagrant box.config.vm.box = 'geerlingguy/ubuntu1604' VirtualBox.config.vm.provider :virtualbox do |v|
end end From: dragon788 [mailto:notifications@github.com] I should have noted that you don't need the angle brackets, they were there On Aug 10, 2016 3:26 PM, "Sam Stamport" notifications@github.com wrote:
— |
Can you post your entire new Vagrantfile and we'll see if there is On Fri, Aug 12, 2016 at 9:36 AM, Sam Stamport notifications@github.com
|
Vagrantfile contents: # -_\- mode: ruby -_-
# vi: set ft=ruby :
Vagrant.configure(2) do |config|
# Vagrant box.
config.vm.box = 'geerlingguy/ubuntu1604'
# VirtualBox.
config.vm.provider :virtualbox do |v|
v.linked_clone = true if Vagrant::VERSION =~ /^1.8/
v.name = vconfig['vagrant_hostname']
v.memory = vconfig['vagrant_memory']
v.cpus = vconfig['vagrant_cpus']
v.customize ['modifyvm', :id, '--natdnshostresolver1', 'on']
v.customize ['modifyvm', :id, '--ioapic', 'on']
end
end |
The problem here is that the |
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. |
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
1.8.4
Run
vagrant -v
to show the version. If you are not running the latest versionof Vagrant, please upgrade before submitting an issue.
Windows 10
This is the operating system that you run locally.
Apache
This is the operating system you run in the virtual machine.
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Using Win 10 PowerShell when I hit the y (or n) key the y should be shown on the screen and then accepted by the script.
What should have happened?
When I typed y and hit enter the y did not show up on the PowerShell window and the script hangs. It works fine with the Windows Command prompt, however.
What actually happened?
Steps to reproduce
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
The text was updated successfully, but these errors were encountered: