Problems detected in kubelet

[ankur0904]

What Happened?

Everything was working fine.
But when I got this error

Exiting due to MK_UNIMPLEMENTED: minikube service is not currently implemented with the builtin network on QEMU

I run this command
minikube start --driver=qemu
Still the error persist, then I run this commands
minikube start --driver qemu --network socket_vmnet
then got this error message

❌  Problems detected in kubelet:
    Nov 17 10:06:55 minikube kubelet[23942]: W1117 10:06:55.712549   23942 reflector.go:533] object-"kube-system"/"kube-root-ca.crt": failed to list *v1.ConfigMap: configmaps "kube-root-ca.crt" is forbidden: User "system:node:minikube" cannot list resource "configmaps" in API group "" in the namespace "kube-system": no relationship found between node 'minikube' and this object
    Nov 17 10:06:55 minikube kubelet[23942]: E1117 10:06:55.712611   23942 reflector.go:148] object-"kube-system"/"kube-root-ca.crt": Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps "kube-root-ca.crt" is forbidden: User "system:node:minikube" cannot list resource "configmaps" in API group "" in the namespace "kube-system": no relationship found between node 'minikube' and this object

After that, running minikube start
also start to give this error.

Attach the log file

logs.txt

Operating System

Ubuntu

Driver

Docker

[kundan2707]

There are many known QEMU driver issue listed here.
#14146

[spowelljr]

The Exiting due to MK_UNIMPLEMENTED error is expected as the builtin network can't support the service command. If you do a minikube delete and then do minikube start --driver qemu --network socket_vmnet again do you get a different error? I see in your logs that you're restarting the cluster, I'm curious what the output would be on a first start.

[kundan2707]

/kind support

[ankur0904]

@spowelljr
Here is the log

ankur@ankur:~$ minikube delete
🔥  Deleting "minikube" in qemu2 ...
💀  Removed all traces of the "minikube" cluster.
ankur@ankur:~$ minikube start --driver qemu --network socket_vmnet
😄  minikube v1.31.2 on Ubuntu 22.04
✨  Using the qemu2 driver based on user configuration

❌  Exiting due to MK_USAGE: The socket_vmnet network is only supported on macOS

When I ran

ankur@ankur:~$ minikube start
😄  minikube v1.31.2 on Ubuntu 22.04
✨  Automatically selected the qemu2 driver. Other choices: virtualbox, ssh
🌐  Automatically selected the builtin network
❗  You are using the QEMU driver without a dedicated network, which doesn't support `minikube service` & `minikube tunnel` commands.
👍  Starting control plane node minikube in cluster minikube
🔥  Creating qemu2 VM (CPUs=2, Memory=3400MB, Disk=20000MB) ...
🎉  minikube 1.32.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.32.0
💡  To disable this notice, run: 'minikube config set WantUpdateNotification false'

🐳  Preparing Kubernetes v1.27.4 on Docker 24.0.4 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔗  Configuring bridge CNI (Container Networking Interface) ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

[spowelljr]

Ah, I missed that you were on Linux, socket_vmnet is only for macOS as the output states. If you're using Linux and want to use QEMU the builtin network is the only option at this time.

[watashiSHUN]

@spowelljr so is there a way for ubuntu user to test their kubernete app with minicluster locally?
https://stackoverflow.com/questions/77637171/how-to-test-kubernetes-app-locally-on-ubuntu

[spowelljr]

@watashiSHUN You'd have to use a different driver, the most popular option is using Docker, KVM is another popular choice, you can see the full list of supported drivers here

https://minikube.sigs.k8s.io/docs/drivers/

[ankur0904]

Ah, I missed that you were on Linux, socket_vmnet is only for macOS as the output states. If you're using Linux and want to use QEMU the builtin network is the only option at this time.

Thanks @spowelljr for the help.

[DhanushNehru]

spowelljr

Thanks for this @spowelljr . Was facing the similar issue with qemu driver in Mac M1

minikube delete
minikube start --driver=docker

actually resolved the issue.

[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