How to install and use Minikube on Fedora 35

Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a single-node Kubernetes cluster inside a VM on your local machine. Kubernetes quickly set up a local Kubernetes cluster on Linux, Windows, and macOS.

It is always advisable before diving into Kubernetes, you will need a minimal Kubernetes setup. Such a setup should spin up fast and integrate well with other tools.

Minikube is the best fit because of the following:

  • It runs on Windows, Linux and MacOS.
  • It supports the latest Kubernetes release
  • It supports multiple container runtimes i.e Containerd, KVM, Docker, Podman etc
  • It has supports for adbvanced features such as Load balancing, Featuregates and filesystems mounts.
  • It has support for Addons. Addons being a marketplace for developers to share configurations for running services on Minikube.
  • It supports CI environments


To run Kubernetes effectively you need to allocate the following to Minikube on your system.

  • 2 CPUs or more
  • 2 GB of memory
  • 20 GB or more of free disk space
  • Reliable internet connections.
  • Conatiner or virtual machine manager such as Docker, KVM, Podman, Virtual Box etc.

Install Minikube on Fedora 35

Let’s now dive into installing and playing with Kubernetes. I am going to be using Podman for running Kubernetes, You can spin up using Docker, Virtualbox, or KVM whichever you understand well.

1. Run system updates

To make sure our repositories are up to date, we need to run system-wide updates on our distro. Open your terminal and input the following command;

$ sudo dnf update -y

When updates are complete, proceed to install download the Minikube binary.

Before we can continue make sure Podman is up and running.

Check this if using Ubuntu distro.

If you opted for VirtualBox on Ubuntu, check this article.

2. Install Podman on Fedora 35.

To install Podman, run the following command.

$ sudo dnf install podman

Sample output.

 podman                                 x86_64            3:3.4.4-1.fc35                updates             12 M
Installing dependencies:
 conmon                                 x86_64            2:2.0.30-2.fc35               fedora              56 k
 container-selinux                      noarch            2:2.170.0-2.fc35              updates             50 k
 containernetworking-plugins            x86_64            1.0.1-1.fc35                  fedora             8.7 M
 containers-common                      noarch            4:1-32.fc35                   updates             76 k
 criu                                   x86_64            3.16.1-2.fc35                 updates            529 k
 criu-libs                              x86_64            3.16.1-2.fc35                 updates             31 k
 crun                                   x86_64            1.3-1.fc35                    updates            174 k
 dnsmasq                                x86_64            2.86-3.fc35                   updates            333 k
 fuse-common                            x86_64            3.10.5-1.fc35                 fedora             8.3 k
 fuse3                                  x86_64            3.10.5-1.fc35                 fedora              54 k
 fuse3-libs                             x86_64            3.10.5-1.fc35                 fedora              92 k
 iptables-legacy                        x86_64            1.8.7-13.fc35                 fedora              53 k
 libbsd                                 x86_64            0.10.0-8.fc35                 fedora             104 k
 libnet                                 x86_64            1.2-4.fc35                    fedora              57 k
 libnftnl                               x86_64            1.2.0-2.fc35                  fedora              82 k
 libslirp                               x86_64            4.6.1-2.fc35                  fedora              72 k
 nftables                               x86_64            1:1.0.0-1.fc35                fedora             373 k
 shadow-utils-subid                     x86_64            2:4.9-8.fc35                  updates             89 k
 yajl                                   x86_64            2.1.0-17.fc35                 fedora              37 k
Installing weak dependencies:
 catatonit                              x86_64            0.1.7-1.fc35                  updates            316 k
 fuse-overlayfs                         x86_64            1.7.1-2.fc35                  fedora              72 k
 podman-gvproxy                         x86_64            3:3.4.4-1.fc35                updates            3.7 M
 podman-plugins                         x86_64            3:3.4.4-1.fc35                updates            2.6 M
 slirp4netns                            x86_64            1.1.12-2.fc35                 fedora              55 k

Transaction Summary
Install  25 Packages

Total download size: 30 M
Installed size: 137 M
Is this ok [y/N]: 

Press y to allow installation to continue. This process will install Podman and its dependencies.

You can check the version of Podman installed with the following command.

$ podman -v
podman version 3.4.4

To run Minikube you need to be using user passwordless sudo. Check this article on how to create user.

When you have set up the user using the following link, proceed to make the user-created passwordless by doing the following;

Uncomment this line from /etc/sudoers. use nano/etc/sudoers command

$ nano/etc/sudoers
# %wheel ALL=(ALL)       NOPASSWD: ALL

3. Download Minikube binary

To download Minikube binary, run the following command and make sure you make it executable for it to function globally.

$ wget -O /usr/local/bin/minikube

Sample output

--2021-12-18 11:05:16--
Resolving (,,, ...
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 69568775 (66M) [application/octet-stream]
Saving to: ‘/usr/local/bin/minikube’

/usr/local/bin/minikube      100%[===========================================>]  66.35M   137MB/s    in 0.5s    

2021-12-18 11:05:18 (137 MB/s) - ‘/usr/local/bin/minikube’ saved [69568775/69568775]

Make it executable with the following command:

$ sudo chmod 0755 /usr/local/bin/minikube 

After all, this is done, make sure you are running a passwordless sudo to make Minikube run efficiently.

If you can be able to run sudo podman ps without asking for a password then you are good to go, but if you can’t run this then you need to ensure you change it to be passwordless.

Let’s check out this;

$ sudo podman ps

4. Configure Minikube to us Podman

Now that we have downloaded our Minikube binary, we can now configure it to use Podman. Use the following command to run the Minikube configuration.

$ minikube config set driver podman

You will be greeted with the following message.

! These changes will take effect upon a minikube delete and then a minikube start

We can run our first instance. Run the following command to initiate the instance.

$ minikube start

If you are getting an error like the one below, ensure you add 2 CPUs and 2GB of memory.

* minikube v1.24.0 on Fedora 35 (kvm/amd64)
* Using the podman driver based on user configuration

X Exiting due to RSRC_INSUFFICIENT_CORES: Requested cpu count 2 is greater than the available cpus of 1

To navigate through the following error, we need to set the number of CPUs to 2, and to do that run the following command to enable 2 CPUs on Podman.

Run podman info to check the configuration of Podman.

$ podman info

To set memory and CPU use the following command;

$ minikube stop

Then set memory

$ minikube config set memory 2048  

Then set CPU

$ minikube config set cpu 2

After this run minikube start

$ minikube start

The output for minikube start is this;

* minikube v1.24.0 on Fedora 35 (kvm/amd64)
* Using the podman driver based on user configuration

X The requested memory allocation of 1965MiB does not leave room for system overhead (total system memory: 1965MiB). You may face stability issues.
* Suggestion: Start minikube with less memory allocated: 'minikube start --memory=1965mb'

* Starting control plane node minikube in cluster minikube
* Pulling base image ...
* Downloading Kubernetes v1.22.3 preload ...
    > preloaded-images-k8s-v13-v1...: 501.73 MiB / 501.73 MiB  100.00% 128.75 M
    > 355.78 MiB / 355.78 MiB  100.00% 27.42 MiB p
E1218 12:37:09.436094   19995 cache.go:201] Error downloading kic artifacts:  not yet implemented, see issue #8426
* Creating podman container (CPUs=2, Memory=1965MB) ...
* Preparing Kubernetes v1.22.3 on Docker 20.10.8 ...
  - Generating certificates and keys ...
  - Booting up control plane ...
  - Configuring RBAC rules ...
* Verifying Kubernetes components...
  - Using image
* Enabled addons: storage-provisioner, default-storageclass
* kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

5. Use kubectl to interact with your cluster

kubectl comes with Minikube so we don’t need to install it.

Let’s see how we use kubectl.

Check the instance with Minikube

$ minikube kubectl get nodes

Output will look like this;

> kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s
    > kubectl: 44.73 MiB / 44.73 MiB [-------------] 100.00% 1.81 GiB p/s 200ms
NAME       STATUS   ROLES                  AGE   VERSION
minikube   Ready    control-plane,master   21m   v1.22.3

Check the instance with kubectl

From what I can see from the output above kubectl was not installed, so I will have to do install manually.

$ cat <<EOF | sudo tee /etc/yum.repos.d/kubernetes.repo

Then install with the following command;

sudo dnf install kubectl -y

You can check the version of installed kubectl with the following command

$ kubectl version

The above command will show both client and server version

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3", GitCommit:"c92036820499fedefec0f847e2054d824aea6cd1", GitTreeState:"clean", BuildDate:"2021-10-27T18:35:25Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}

You might need also to get the cluster info, you can use the following command;

$ kubectl cluster-info
Kubernetes control plane is running at
CoreDNS is running at

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

Now, you can run kubectl get nodes. This time it will run successfully.

$ kubectl get nodes 
NAME       STATUS   ROLES                  AGE   VERSION
minikube   Ready    control-plane,master   54m   v1.22.3

To see the minikube dashboard run the following command;

$ minikube dashboard

Sample output will look like this;

* Enabling dashboard ...
  - Using image kubernetesui/dashboard:v2.3.1
  - Using image kubernetesui/metrics-scraper:v1.0.7
* Verifying dashboard health ...
* Launching proxy ...
* Verifying proxy health ...
* Opening in your default browser...

Open your favorite browser and access Kubernetes


We have successfully installed Minikube on Fedora 35 and learned how to configure it. In case of a problem, you can consult Minikube documentation.

About Kipkoech Sang

I am a technology enthusiast who loves to share gained knowledge through offering daily tips as a way of empowering others. I am fan of Linux and all other things open source.
View all posts by Kipkoech Sang →

Leave a Reply

Your email address will not be published.