actions-setup-minikube icon indicating copy to clipboard operation
actions-setup-minikube copied to clipboard

Kubernetes 1.20.2 requires conntrack

Open Khuzha opened this issue 4 years ago โ€ข 27 comments

Hello, I got this problem during installing minikube and found the same issue here, but it's closed and @manusa wrote that he's gonna fix it. Maybe my case is new:)


$ minikube start --vm-driver=none
๐Ÿ˜„  minikube v1.17.1 on Ubuntu 20.04
โœจ  Using the none driver based on user configuration

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

Khuzha avatar Feb 15 '21 14:02 Khuzha

Hi @Khuzha.

This is not the Minikube repository, but a repository for a GitHub Action that deploy Minikube in your pipeline.

From you comment I guess you're not using this action but trying to start Minikube in your local environment. If that's the case, the solution described in this comment should work for you.

If that's not the case, please provide a link to the repo where you're running the GH action (if it's public). Or at least some more information like the version of manusa/actions-setup-minikube you are using.

manusa avatar Feb 15 '21 14:02 manusa

Hello, I got this problem during installing minikube and found the same issue here, but it's closed and @manusa wrote that he's gonna fix it. Maybe my case is new:)


$ minikube start --vm-driver=none
๐Ÿ˜„  minikube v1.17.1 on Ubuntu 20.04
โœจ  Using the none driver based on user configuration

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

install and soft link slove same problem. sudo apt-get install -y conntrack root@debian:/usr/sbin# cd /usr/bin/ root@debian:/usr/bin# ln -s /usr/sbin/conntrack conntrack

root@debian:/usr/bin# minikube start --driver=none ๐Ÿ˜„ Debian 10.8 (vbox/amd64) ไธŠ็š„ minikube v1.17.1 โœจ ๆ นๆฎ็”จๆˆท้…็ฝฎไฝฟ็”จ none ้ฉฑๅŠจ็จ‹ๅบ ๐Ÿ‘ Starting control plane node minikube in cluster minikube ๐Ÿคน Running on localhost (CPUs=6, Memory=3946MB, Disk=28031MB) ... โ„น๏ธ OS release is Debian GNU/Linux 10 (buster) > kubeadm.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s > kubelet.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s > kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s > kubectl: 38.37 MiB / 38.37 MiB [----------------] 100.00% 9.78 MiB p/s 5s > kubeadm: 37.40 MiB / 37.40 MiB [---------------] 100.00% 3.50 MiB p/s 11s > kubelet: 108.73 MiB / 108.73 MiB [-------------] 100.00% 6.99 MiB p/s 16s

enjolras1205 avatar Feb 27 '21 06:02 enjolras1205

The same issue i meet

root@tashen-test-3534063:~# minikube start --vm-driver=none
๐Ÿ˜„  minikube v1.18.1 on Ubuntu 18.04 (kvm/amd64)
โœจ  Using the none driver based on user configuration

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

smileusd avatar Apr 09 '21 10:04 smileusd

hi @Khuzha Use command : sudo apt-get install -y conntrack then following by: sudo -E minikube start --driver=none it worked for me :)

ashraf7121 avatar May 21 '21 20:05 ashraf7121

arch linux install:

pacman -S conntrack-tools

and run:

sudo minikube start --vm-driver=none

all ok!

juanluiscb avatar Jul 27 '21 21:07 juanluiscb

apt install conntrack

forging2012 avatar Feb 26 '22 04:02 forging2012

I have tried all ways but same error

mfaraz669 avatar Jun 14 '23 11:06 mfaraz669

sudo minikube start --vm-driver=none --force

it will work

bunny568 avatar Jun 29 '23 12:06 bunny568

After installing the contrack sudo apt-get install -y conntrack sudo minikube start --vm-driver=none --force ๐Ÿ˜„ minikube v1.30.1 on Ubuntu 22.04 (amd64) โ— minikube skips various validations when --force is supplied; this may lead to unexpected behavior โœจ Using the none driver based on user configuration

โŒ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.26.3 requires crictl to be installed in root's path

Tried to install crictl as below command, but unfortunately getting as below. sudo apt-get install crictl Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package crictl

sudo minikube start --vm-driver=none ๐Ÿ˜„ minikube v1.30.1 on Ubuntu 22.04 (amd64) โœจ Using the none driver based on user configuration

โŒ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.26.3 requires crictl to be installed in root's path

Can any one suggest what exactly do i need to install here. I'm using WSL Ubuntu 22.04 (amd64)

viswa2 avatar Jul 12 '23 07:07 viswa2

Install docker first and then try to install minikube

mfaraz669 avatar Jul 12 '23 07:07 mfaraz669

Yes, i have installed docker and trying to installing the minikube getting as per the above. docker -v Docker version 20.10.21, build 20.10.21-0ubuntu1~22.04.3

viswa2 avatar Jul 12 '23 07:07 viswa2

use sudo minikube start --force

it worked for me

Jaideep1702 avatar Jul 13 '23 13:07 Jaideep1702

thanks it works

abhijeet1680 avatar Jul 15 '23 04:07 abhijeet1680

Hello @Jaideep1702 Thanks it's works, but whenever WSL ubuntu closes, again it's need to run sudo minikube start --force command. Is it normal behavior or how it is?

viswa2 avatar Jul 16 '23 14:07 viswa2

Hello @Jaideep1702 Thanks it's works, but whenever WSL ubuntu closes, again it's need to run sudo minikube start --force command. Is it normal behavior or how it is?

It is normal mostly I didn't face any error

Jaideep1702 avatar Jul 17 '23 04:07 Jaideep1702

use sudo minikube start --force

it worked for me

awstraining9986 avatar Jul 21 '23 11:07 awstraining9986

sudo minikube start --force worked for me

zeal-user avatar Jul 29 '23 18:07 zeal-user

sudo minikube start --vm-driver=none --force

still same error

noobtuber20103152 avatar Aug 26 '23 13:08 noobtuber20103152

getting same error ???

LeulAria avatar Sep 09 '23 06:09 LeulAria

minikube start --force working like a charm thanks

thammansingh avatar Sep 11 '23 06:09 thammansingh

sudo minikube start --force work

Daksh0636 avatar Oct 21 '23 06:10 Daksh0636

minikube start --force

Thank you Jaideep, it worked :)

Pooja1200 avatar Dec 03 '23 07:12 Pooja1200

sudo minikube start --force

it worked for me

boughanmirania avatar Dec 11 '23 23:12 boughanmirania

minikube start --vm-driver=none ๐Ÿ˜„ minikube v1.32.0 on Ubuntu 20.04 โœจ Using the none driver based on user configuration

โŒ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.28.3 requires crictl to be installed in root's path Action: wget https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.26.0/crictl-v1.26.0-linux-amd64.tar.gz sudo tar zxvf crictl-v1.26.0-linux-amd64.tar.gz -C /usr/local/bin

minikube start --vm-driver=none ๐Ÿ˜„ minikube v1.32.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=4, Memory=31573MB, Disk=29587MB) ...

๐Ÿณ Exiting due to NOT_FOUND_CRI_DOCKERD:

๐Ÿ’ก Suggestion:

The none driver with Kubernetes v1.24+ and the docker container-runtime requires cri-dockerd.

Please install cri-dockerd using these instructions:

https://github.com/Mirantis/cri-dockerd

Action : wget https://github.com/Mirantis/cri-dockerd/releases/download/v0.3.9/cri-dockerd_0.3.9.3-0.ubuntu-focal_amd64.deb dpkg -i cri-dockerd_0.3.9.3-0.ubuntu-focal_amd64.deb

minikube start --vm-driver=none ๐Ÿ˜„ minikube v1.32.0 on Ubuntu 20.04 โœจ Using the none driver based on existing profile ๐Ÿ‘ Starting control plane node minikube in cluster minikube ๐Ÿ”„ Restarting existing none bare metal machine for "minikube" ...

๐Ÿ”— Exiting due to NOT_FOUND_CNI_PLUGINS:

๐Ÿ’ก Suggestion:

The none driver with Kubernetes v1.24+ requires containernetworking-plugins.

Please install containernetworking-plugins using these instructions:

https://minikube.sigs.k8s.io/docs/faq/#how-do-i-install-containernetworking-plugins-for-none-driver

Action: create a file and run it to install cni-plugin e.g cat plugin.sh CNI_PLUGIN_VERSION="v1.4.0" CNI_PLUGIN_TAR="cni-plugins-linux-amd64-$CNI_PLUGIN_VERSION.tgz" # change arch if not on amd64 CNI_PLUGIN_INSTALL_DIR="/opt/cni/bin"

#https://github.com/containernetworking/plugins/releases/download/v1.4.0/cni-plugins-linux-amd64-v1.4.0.tgz curl -LO "https://github.com/containernetworking/plugins/releases/download/$CNI_PLUGIN_VERSION/$CNI_PLUGIN_TAR" sudo mkdir -p "$CNI_PLUGIN_INSTALL_DIR" sudo tar -xf "$CNI_PLUGIN_TAR" -C "$CNI_PLUGIN_INSTALL_DIR" rm "$CNI_PLUGIN_TAR"

--- run sh plugin.sh


minikube start --vm-driver=none success : Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

sanjay92-gupta avatar Feb 01 '24 22:02 sanjay92-gupta

after above it worked but all things are stopped

type: Control Plane host: Stopped kubelet: Stopped apiserver: Stopped kubeconfig: Stopped

ganeshjag4 avatar Feb 02 '24 09:02 ganeshjag4

Yeahhhh !!!!! This Worked for mee .....Thanks Alot @sanjay92-gupta

sumitghosh922 avatar Feb 21 '24 17:02 sumitghosh922

update 2024:

# KUBECTL:
sudo apt-get update
# apt-transport-https may be a dummy package; if so, you can skip that package
sudo apt-get install -y apt-transport-https ca-certificates curl gnupg
# If the folder `/etc/apt/keyrings` does not exist, it should be created before the curl command, read the note below.
# sudo mkdir -p -m 755 /etc/apt/keyrings
curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.30/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
sudo chmod 644 /etc/apt/keyrings/kubernetes-apt-keyring.gpg # allow unprivileged APT programs to read this keyring
# This overwrites any existing configuration in /etc/apt/sources.list.d/kubernetes.list
echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.30/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list
sudo chmod 644 /etc/apt/sources.list.d/kubernetes.list   # helps tools such as command-not-found to work correctly
sudo apt-get update
sudo apt-get install -y kubectl
echo 'source /etc/bash_completion' >>~/.bashrc
echo 'source <(kubectl completion bash)' >>~/.bashrc
source ~/.bashrc

# DOCKER:
wget https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/containerd.io_1.6.31-1_amd64.deb
wget https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/docker-ce_26.1.3-1~ubuntu.22.04~jammy_amd64.deb
wget https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/docker-ce-cli_26.1.3-1~ubuntu.22.04~jammy_amd64.deb
wget https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/docker-buildx-plugin_0.14.0-1~ubuntu.22.04~jammy_amd64.deb
wget https://download.docker.com/linux/ubuntu/dists/jammy/pool/stable/amd64/docker-compose-plugin_2.6.0~ubuntu-jammy_amd64.deb
sudo dpkg -i ./containerd.io_1.6.31-1_amd64.deb
sudo dpkg -i ./docker-ce-cli_26.1.3-1~ubuntu.22.04~jammy_amd64.deb
sudo dpkg -i ./docker-ce_26.1.3-1~ubuntu.22.04~jammy_amd64.deb
sudo dpkg -i ./docker-buildx-plugin_0.14.0-1~ubuntu.22.04~jammy_amd64.deb
sudo dpkg -i ./docker-compose-plugin_2.6.0~ubuntu-jammy_amd64.deb
sudo service docker start

# MINIKUBE:
wget https://github.com/kubernetes/minikube/releases/download/v1.33.1/minikube_1.33.1-0_amd64.deb
sudo dpkg -i ./minikube_1.33.1-0_amd64.deb
minikube version
sudo apt -y install conntrack
wget https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.30.0/crictl-v1.30.0-linux-amd64.tar.gz
sudo tar zxvf crictl-v1.30.0-linux-amd64.tar.gz -C /usr/local/bin
wget https://github.com/Mirantis/cri-dockerd/releases/download/v0.3.14/cri-dockerd_0.3.14.3-0.ubuntu-jammy_amd64.deb
sudo dpkg -i ./cri-dockerd_0.3.14.3-0.ubuntu-jammy_amd64.deb
wget https://github.com/containernetworking/plugins/releases/download/v1.5.0/cni-plugins-linux-amd64-v1.5.0.tgz
sudo mkdir -p /opt/cni/bin
sudo tar -xf cni-plugins-linux-amd64-v1.5.0.tgz -C /opt/cni/bin
sudo mkdir -p /etc/cni/net.d
minikube start --vm-driver=none

bokhanych avatar May 22 '24 11:05 bokhanych