[Solved] GUEST MISSING CONNTRACK Kubernetes 1.22.3 requires conntrack to be installed in root’s path

Error:-

navdeepd2@test:~$ sudo minikube start –driver=none
๐Ÿ˜„ minikube v1.24.0 on Ubuntu 20.04
โœจ Using the none driver based on user configuration

โŒ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.22.3 requires conntrack to be installed in root’s path

Solution:-

navdeepd2@test:~$ sudo apt-get install -y conntrack

Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libfprint-2-tod1 libllvm10
Use ‘sudo apt autoremove’ to remove them.
Suggested packages:
nftables
The following NEW packages will be installed:
conntrack
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 30.3 kB of archives.
After this operation, 104 kB of additional disk space will be used.
Get:1 http://in.archive.ubuntu.com/ubuntu focal/main amd64 conntrack amd64 1:1.4.5-2 [30.3 kB]
Fetched 30.3 kB in 0s (274 kB/s)
Selecting previously unselected package conntrack.
(Reading database … 256173 files and directories currently installed.)
Preparing to unpack …/conntrack_1%3a1.4.5-2_amd64.deb …
Unpacking conntrack (1:1.4.5-2) …
Setting up conntrack (1:1.4.5-2) …
Processing triggers for man-db (2.9.1-1) …

navdeepd2@test:~$ sudo minikube start --driver=none

๐Ÿ˜„ minikube v1.24.0 on Ubuntu 20.04
โœจ Using the none driver based on user configuration
๐Ÿ‘ Starting control plane node minikube in cluster minikube
๐Ÿคน Running on localhost (CPUs=3, Memory=5871MB, Disk=37832MB) …
โ„น๏ธ OS release is Ubuntu 20.04.3 LTS
๐Ÿณ Preparing Kubernetes v1.22.3 on Docker 20.10.11 …
โ–ช kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
> kubelet.sha256: 64 B / 64 B [————————–] 100.00% ? p/s 0s
> kubeadm.sha256: 64 B / 64 B [————————–] 100.00% ? p/s 0s
> kubectl.sha256: 64 B / 64 B [————————–] 100.00% ? p/s 0s
> kubectl: 44.73 MiB / 44.73 MiB [————–] 100.00% 6.03 MiB p/s 7.6s
> kubelet: 115.57 MiB / 115.57 MiB [————-] 100.00% 9.55 MiB p/s 12s
> kubeadm: 43.71 MiB / 43.71 MiB [—————] 100.00% 3.04 MiB p/s 15s
โ–ช Generating certificates and keys …
โ–ช Booting up control plane …
โ–ช Configuring RBAC rules …
๐Ÿคน Configuring local host environment …

โ— The ‘none’ driver is designed for experts who need to integrate with an existing VM
๐Ÿ’ก Most users should use the newer ‘docker’ driver instead, which does not require root!
๐Ÿ“˜ For more information, see: https://minikube.sigs.k8s.io/docs/reference/drivers/none/

โ— kubectl and minikube configuration will be stored in /root
โ— To use kubectl or minikube commands as your own user, you may need to relocate them. For example, to overwrite your own settings, run:

โ–ช sudo mv /root/.kube /root/.minikube $HOME
โ–ช sudo chown -R $USER $HOME/.kube $HOME/.minikube

๐Ÿ’ก This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true
๐Ÿ”Ž Verifying Kubernetes components…
โ–ช Using image gcr.io/k8s-minikube/storage-provisioner:v5
๐ŸŒŸ Enabled addons: storage-provisioner, default-storageclass
๐Ÿ„ Done! kubectl is now configured to use “minikube” cluster and “default” namespace by default

 

Leave a Reply