-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
laravel/homestead could not be found #1982
Comments
I've same issue. Updated to latest homestead, destroyed image.. and now can't work ^_^ homestead/scripts/homestead.rb Line 22 in 98a798b
to config.vm.box_version = settings['version'] ||= '>= 14.0.1'
After that |
my solution (too bad I had to find out myself): change the vagrant installation to AMD64, instead Intel 32bit. I really can't appreciate the support and bad documentation. |
downgraded to vagrant 2.4.0, no luck. |
@tjerkhamer i ended up doing the same thing you did and it seems to work. |
Versions
I'm using a complete fresh / new install for my pc
Host operating system
Windows 10
Homestead.yaml
Vagrant destroy & up output
[Provide a link to a GitHub Gist containing the complete output of
vagrant destroy && vagrant up
.](https://gist.github.com/tjerkhamer/8281b6122cf2603ac10f2b3ce9224c62)Do NOT paste the debug output in the issue, just paste the link to the Gist.
Expected behavior
I would expect the homestead box to be created as described in the documentation
Actual behavior
Vagrant up is not possible, laravel/homestead could not be found and is not downloading from vagrantcloud.com
Steps to reproduce
The text was updated successfully, but these errors were encountered: