Call out in docs which minikube drivers support Apple Silicon

[danielhelfand]

What Happened?

I was attempting to run minikube without using Docker on an m1 mac. I eventually gave up and ended up using Docker as it seems the other options really don't support Apple silicon yet. I am assuming that Docker is the only real option at this point. All the others mentioned (i.e. VirtualBox, hyperkit/podman, vmware, parallels) do not seem to work at this point.

It's pretty well documented in GitHub issues that m1 support is still a WIP, but calling out in the drivers doc about m1 support/updating over time might help users with the situation.

Attach the log file

N/A

Operating System

macOS (Default)

Driver

No response

[danielhelfand]

Happy to pick this up if all the details above look right.

[afbjorklund]

Both vmware and parallels are supposed to work, but you also need an ISO that supports arm64.

They are also proprietary, so you end up with like $200 or $100 (compared with the $60 or so for Docker)

However, hyperkit will not work so we need to resurrect the "qemu" driver and use that instead...

Another option would be to use Lima, which will use ubuntu and containerd to run kubeadm: k8s.yaml

---

brew install lima

limactl start https://raw.githubusercontent.com/lima-vm/lima/master/examples/k8s.yaml

• MEP: Change from custom Buildroot ISO to standard Kubernetes OS #9992

• MEP: CRI: Containerd by default, Buildkitd on demand #9639

[afbjorklund]

Docker is still the "preferred" driver and "default" runtime.

[danielhelfand]

@afbjorklund Appreciate you filling me in on the state of things. Let me try to distill some of this information into some minor doc edits.

[afbjorklund]

Not sure about Podman support, maybe revisit once Podman Desktop 4.0.0 is out and once it has been tested ?

• Podman Desktop driver on Mac or Win (and Linux) #8003

As far as I know now, it will not feature Kubernetes (like Docker Desktop or Rancher Desktop) - you need CRC.

• https://developers.redhat.com/products/codeready-containers

[afbjorklund]

Users are supposed to be able to find out their OS ("Darwin") and Arch ("aarch64"), in order to install binaries.

It would be nice if we used similiar wording here, even though it is fine to call it macOS and arm64 of course.

"Apple silicon" this, "Intel silicon" that.

Preferrably, both would be invisible.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.