I think I'm going to stop providing Homestead base box builds on Hyper-V and VMware.
Would this negatively affect you?
Tell me about it via email: First at First Last dot Me
Subject "Homestead Providers"
For clarity's sake, you can comment here. Or email me if you'd prefer not to post publicly.
Not using either, will not affect me.
@svpernova09 Please, please continue to provide vmware. It will affect our work as we all have vmware virtualizations for homestead.
@svpernova09 Please, please continue to provide vmware. It will affect our work as we all have vmware virtualizations for homestead.
Thanks for the feedback: note despite the docs currently having removed mentions of VMware and Hyper-V I am planning on supporting VMware w/ Homestead base box 11.0.0, I'm just having an issue building the box currently which is why it's not currently available.
Joe and I discussed this in Slack a bit, but adding here for completeness.
I think it's important to maintain at least one virtualization software that will support Apple M1. Virtualbox is mostly mum on the issue right now, but doesn't appear to be very interested in it. Parallels has said they will support it.
This will affect some of our developer's workflows, as some of our developers run Windows and have a Homestead setup for our larger Laravel apps as well as Docker for a few smaller apps, meaning they are forced to use Hyper-V rather than VirtualBox (like we're all honestly prefer)
@Sn0wCrack I've managed to figure a workaround. I have Hyper-V enabled and am using Docker as well as VirtualBox at the same time.
Key to getting VirtualBox working is when running vagrant up to have the Oracle VirtualBox window open and click on the site your starting up so it's focused on the right side. The issue where Vagrant can't connect via SSH disappears and the box starts right now.
Not ideal but a workaround to get things working immediately.
As a follow up, I'm commited to publishing a VMware base box for the new version of Settler. There will be a VMware base box for v11.0.0 whenever I can get past the current blockers of building the image on VMware.
Closing this issue. I'm going to stop providing Hyper-V builds. There will be at least one more VMware release whenever I can get past the current blockers of building the image on VMware.
Most helpful comment
Joe and I discussed this in Slack a bit, but adding here for completeness.
I think it's important to maintain at least one virtualization software that will support Apple M1. Virtualbox is mostly mum on the issue right now, but doesn't appear to be very interested in it. Parallels has said they will support it.