laravel / homestead

MIT License
3.87k stars 1.44k forks source link

laravel/homestead could not be found #1982

Open tjerkhamer opened 5 months ago

tjerkhamer commented 5 months ago

Versions

I'm using a complete fresh / new install for my pc

Host operating system

Windows 10

Homestead.yaml

---
ip: "192.168.56.56"
memory: 2048
cpus: 2
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
  - ~/.ssh/id_rsa

folders:
  - map: ~/code
    to: /home/vagrant/code

sites:
  - map: homestead.test
    to: /home/vagrant/code/public

databases:
  - homestead

features:
  - mariadb: false
  - postgresql: false
  - ohmyzsh: false
  - webdriver: false

services:
  - enabled:
      - "mysql"

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

  1. clean windows install
  2. git clone https://github.com/laravel/homestead.git ~/Homestead
  3. git checkout release
  4. ./init.bat
  5. vagrant up
marechenok commented 3 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

walterbamert commented 3 months ago

same issue here except i can't get it to work with changing the version to 14.0.1. vagrant-error

tjerkhamer commented 3 months ago

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.

walterbamert commented 3 months ago

downgraded to vagrant 2.4.0, no luck.

walterbamert commented 3 months ago

@tjerkhamer i ended up doing the same thing you did and it seems to work.