Open tjerkhamer opened 5 months ago
I've same issue. Updated to latest homestead, destroyed image.. and now can't work ^_^
Okay, fixed it. Updated vagrant to 2.4.1 and edited
https://github.com/laravel/homestead/blob/98a798b18a078121252f0ecfe3e10cba050ce504/scripts/homestead.rb#L22
to
config.vm.box_version = settings['version'] ||= '>= 14.0.1'
After that vagrant up
downloaded latest 14.0.2 box
same issue here except i can't get it to work with changing the version to 14.0.1.
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](https://gist.github.com/) containing the complete output of
vagrant destroy && vagrant up
. 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