Error with Minikube Hyperkit

[digitalcrest01]

What Happened?

Error due to MK_CONFIG_SET: Set failed: run validations for "driver" with value of "hyperkit": [driver "hyperkit" is not supported]

Attach the log file

• /var/folders/tx/g4gjlqxd7cgdwp2v05_sbz7h0000gn/T/minikube_config_559a34aefd80a1002cb956d65d32e9c1bcc8acb0_0.log

Operating System

macOS (Default)

Driver

HyperKit

[spowelljr]

Hi @digitalcrest01, are you trying to run this on an M1 or M2 machine? Apple arm64 machines don't have HyperKit so you you'll have to use Docker or QEMU.

[caerulescens]

@digitalcrest01 hyperkit has x86 specific code, and will not run on arm64; see moby/hyperkit#303 (comment). It's being tracked here: moby/hyperkit#310.

On m-series processors, you can use qemu2 driver and socket_vmnet network to get the essential minikube functionality on macos.

1. Install qemu.
2. Install socket_vmnet.
3. I think you will need to start the network like mentioned here in the docs.
4. Run minikube start --driver=qemu2 --network=socket_vmnet
5. Test minikube tunnel in a separate terminal window.

[caerulescens]

I think this issue can be closed; I don't think hyperkit is going to be ported to arm64 as it's being phased out in favor of qemu2 and framework.virtualization, iirc.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[caerulescens]

/close

[k8s-ci-robot]

@caerulescens: Closing this issue.

In response to this:

/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-sigs/prow repository.