-
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 up hanging #8779
Comments
I am having the exact same issue today :( |
Same issue here. I am on Arch Linux. The problem started yesterday out of nowhere. After |
Could you please either delete my issue or delete it whatever I don't feel like filling up my issues list with reports I spent hours writing and no one bothered even answering to it. Yes I am angry. |
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!
Vagrant version
Run
vagrant -v
to show the version. If you are not running the latest versionof Vagrant, please upgrade before submitting an issue.
vagrant -v
Host operating system
This is the operating system that you run locally.
OS Name: Microsoft Windows 7 Ultimate
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
BIOS Version: Dell Inc. A11, 11/22/2016
Guest operating system
This is the operating system you run in the virtual machine.
Vagrantfile
ruby
Copy-paste your Vagrantfile here
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.
https://gist.github.com/amezarashi97/85c6c9d9308929da683c1f49ca1a7129
Expected behavior
What should have happened?
I don't know it's the first time I'm running both the process and vagrant.
Actual behavior
What actually happened?
Command line got hung
Steps to reproduce
1. Read my mindReferences
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
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!
Took me too much time to write this I recommend that you automatize this process some more thanks for the great stuff btw.
The text was updated successfully, but these errors were encountered: