Skip to content
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

Closed
ghost opened this issue Jul 13, 2017 · 4 comments
Closed

vagrant up hanging #8779

ghost opened this issue Jul 13, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Jul 13, 2017

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 version
of 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

# vi: set ft=ruby :

Vagrant.configure("2") do |config|

    config.vm.box = "scotch/box"
    config.vm.network "private_network", ip: "192.168.33.10"
    config.vm.hostname = "scotchbox"
    config.vm.synced_folder ".", "/var/www", :mount_options => ["dmode=777", "fm
ode=666"]

    # Optional NFS. Make sure to remove other synced_folder line too
    #config.vm.synced_folder ".", "/var/www", :nfs => { :mount_options => ["dmod
e=777","fmode=666"] }

end

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 mind

git clone https://github.com/scotch-io/scotch-box my-project
cd my-project
vagrant up

References

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.

@hopoffbaby
Copy link

I am having the exact same issue today :(

#8777

@pnedkov
Copy link

pnedkov commented Jul 13, 2017

Same issue here. I am on Arch Linux. The problem started yesterday out of nowhere. After vagrant up it just hangs at SSH auth method: private key but the machine is up and running and accessible over the network. Upgrading from 1.9.6 to 1.9.7 did not make any difference. Any suggestions?

@ghost
Copy link
Author

ghost commented Jul 16, 2017

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.

@ghost ghost closed this as completed Jul 16, 2017
@ghost
Copy link

ghost commented Apr 1, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants