Closed ethanclevenger91 closed 3 years ago
The answer here is to vagrant destroy,
vagrant upto get back to a known working state.
vagrant reload --provision` isn't idempotent and can certainly fail over time. Sounds like something is causing the default vagrant share to disconnect, this indicates the issue is farther down the toolchain (specifically the Virtualbox provider in this case) than what Homestead can affect.
Versions
Host operating system
Windows 10 Pro 21H1 19043.1202
Homestead.yaml
Vagrant destroy & up output
Gist
Expected behavior
vagrant up
andvagrant reload --provision
should both successfully start the guest.Actual behavior
After a few days of regular use, the box will eventually stop starting successfully on the above commands. The guest interface shows:
And this will kind of loop, so far as I can tell, until the
vagrant up
process times out. I say "so far as I can tell" because if I open VirtualBox and enter the guest GUI, it will proceed to start, showing:Before moving to the login interface.
Once I've entered the guest GUI to break up whatever is stopping successful startup, if I
halt
andup
again, it'll do so without issue until, eventually, the issue manifests again.My best guess is perhaps Windows tries to install updates and restarts the computer without halting the box, causing the issue, but that's simply a guess.
Steps to reproduce
vagrant halt
after initialup
vagrant up
again.vagrant halt
vagrant up