Minikube Wont start on Fedora 37 with Docker Driver because Kubelet process does not start

[amolgautam25]

What Happened?

Fresh Installation of Fedora 37.
Installed Docker , and installed Minikube.
Docker seems to work fine , but minikube fails to start.

Reason: Cant connect to kubelet service. You may inspect logs further but from what i understand , kubelet service is not being installed correctly. I will attach logs to this issue.

After installing minikube, and after multiple failed attempts for a cluster creation i get this:
[gamol@gamol-z01 ~]$ systemctl enable kubelet.service Failed to enable unit: Unit file kubelet.service does not exist.

[gamol@gamol-z01 ~]$ journalctl -xeu kubelet has no entries.

Which makes me believe that kubelet service was not installed properly.

I am on Fedora 37. Have tried with latest patches as well.

Attach the log file

minikube_error.log

Operating System

Redhat/Fedora

Driver

Docker

[amolgautam25]

minikube_error.log

[afbjorklund]

You need to run the systemd commands under minikube ssh (on the node), not on the host.

[andrfaren]

Having the same issue. Fresh install of Fedora 37, Docker and minikube. Unable to start minikube.

[andrfaren]

You need to run the systemd commands under minikube ssh (on the node), not on the host.

Doesn't minikube have to be running in order to run minikube ssh? The problem we're having is that minikube doesn't start in the first place.

[afbjorklund]

Sure, the self-destruct feature makes it harder to get logs (before it is deleted)

But it is still normal that there is no kubelet service in the host (only in the minikube "node")

[andrfaren]

Tried steps in OP in fresh install of Ubuntu instead of Fedora and everything worked.

[andrfaren]

Ran minikube v1.26.0-beta version. Works on Fedora 37. Seems like Fedora 37 and minikube 1.28.0 don't work together.

[afbjorklund]

I don't think anyone tried Fedora, could it be selinux ?

• Add CI testing for Fedora & CentOS #3552

[mnk]

I think this problem is related to Btrfs. I can reproduce the problem when doing a Fedora 37 install with default Btrfs setup, but when selecting Ext4 for the root file system during install, Minikube 1.28.0 works almost(#15573) as expected.

With Btrfs, kubelet fails to start with this error message:

minikube kubelet[14140]: E0102 16:22:03.156579   14140 run.go:74] "command failed" err="failed to set feature gates from initial flags-based config: cannot set feature gate LocalStorageCapacityIsolation to false, feature is locked to true"

[afbjorklund]

Might need some other workaround then, similar to:

• fix kubelet localStorageCapacityIsolation option #15336

[mnk]

A minikube built from master as of today, seems to work fine on Fedora 37 with Btrfs and Kubernetes v1.25.3.

Until we have a new minikube release, a workaround is to run with Kubernetes version < 1.25:

minikube start --kubernetes-version=v1.24.9

[amolgautam25]

Thanks for looking into the issue.
It seems this has been resolved. minikube version v1.29.0 works as expected on fedora 37.