So I decided to play with and learn laravel. I’ve tried several different options, all met with disaster.
So today git cloned Bruno Skvorc’s homestead_improved vagrant box and followed the instructions (from 2014)
I have multiple vagrant boxes on my machine that all run and work as one would expect (Win10 Pro machine with 32GB of RAM)
So when I issued the command (in git bash) vagrant up, the box appears to be booting just fine then quits not running the box with the following verbose error message.
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Stderr: VBoxManage.exe: error: Failed to open/create the internal network ‘HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #6’ (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
I apologize for the long winded error message.
It appears to be a network error. The homestead.yaml file shows a hardwired ip address of: 192.168.10.10
To be honest I’ve never had success with a hardwired IP address. Prefer public_network address on my own subnet.
Yea, that would be great if swader answered but it’s the weekend
I think my issues may stem from having more than one instance of homestead and homestead_improved on my computer. While all of these instances are in separate folders I’m guessing I’ve run out of network interfaces in virtualbox.
I deleted all of my homestead_improved VM’s.
I have one vagrant box downloaded from the vagrantup website. I have laravel installed and I can run the command php artisan serve and I see that the local development server is running on port 8000. I am unable to see the welcome to laravel page though no matter what I do.
Moving on, I went over to github and cloned Bruno Skvorc’s homestead_improved project, into a new subdirectory.
Once again running vagrant up produces an error message “unable to open/create the internal network”.
Virtualbox is up to date, vagrant is up to date and all of my other normal vagrant boxes boot without issue.
To date the only instance of Laravel that I’ve managed to install and see the “Welcome to Laravel” page is on codeanywhere a cloud based IDE. I’ve tried creating a new droplet on Digital Ocean and installed Laravel but when I type laravel , all I see is the message command not found. Very frustrating and I’m to the point of moving on and trying a different PHP framework.
Any suggestions?
so, homestead improved has nothing to do with Laravel, and doesn’t care about the code you use on it. It is also quite different from the original homestead in that it doesn’t require you to install PHP or composer on your main machine to run it, and it lends itself nicely to a VM per project setup, something that the original does not really support. You can choose your own IP address in Homestead.yaml if you don’t like the default one, but it shouldn’t matter because when you do vagrant halt that IP address is freed up anyway. I have a dozen homestead improved projects on my machine, and all but one are halted (I work on only one at any given time). In the case when and if I do need two running at the same times (almost never) I just put one of the IPs to .11 rather than .10, and it all works again.
Regarding your error message - have you tried this?
My issue is that the homestead improved vagrant box fails to boot. It goes through the initial setup just fine but fails booting the vm.
I’ve been using vagrant for over a year now without any issues and the original homestead boxes work.
I have changed IP’s on vagrant boxes too and I’ve had more than one running. This whole evolution was so I could install composer, and then laravel as I learn this new framework. Currently I installed laravel into my Linux Minut VM (not vagrant) which I’ve used for web dev work and PHP work. It’s working great, even PHPStorm runs in this VM fine.
Thanks, I’ll take another look at this when I get a chance later this week. I’m sure there’s something in my configuration for vagrant or virtualbox.
No I have not tried looking at my network interface configuration here in Windows 10 but I’ll give it a try later today, thanks for pointing out the link!
