forked from docker/machine
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VirtualBox: Host-only Adapter deprecated in macOS 13 (Ventura) #38
Comments
spowelljr
changed the title
Host-only Adapter deprecated in macOS 13 (Ventura)
VirtualBox: Host-only Adapter deprecated in macOS 13 (Ventura)
Nov 30, 2022
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
My company recently requested us to upgrade our macOS to 13, so, for us, this is pretty much a big pain point for us... |
Currently the workaround is to use another driver, such as the QEMU driver - that also supports ARM, not only Intel https://github.com/afbjorklund/docker-machine-driver-qemu (if using minikube, there is a "qemu2" driver there) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been getting a large number of reports of users on minikube unable to use the VirtualBox driver on macOS 13. This seems to be due to Host-only Adapter being deprecated, it will need to be replaced with Host-only Network. For backwards compatibility I'm assuming we should only use Host-only Network if the user is on macOS 13 or later.
kubernetes/minikube#15274
The text was updated successfully, but these errors were encountered: