Minikube: none driver integration tests: k8s 1.18 needs conntrack installed

Created on 23 Mar 2020 · 3Comments · Source: kubernetes/minikube

sudo out/minikube start --driver=none --kubernetes-version=1.18.0-rc.1
😄  minikube v1.9.0-beta.2 on Ubuntu 18.04
✨  Using the none driver based on user configuration
🤹  Running on localhost (CPUs=2, Memory=7470MB, Disk=9749MB) ...
ℹ️   OS release is Ubuntu 18.04.3 LTS
🐳  Preparing Kubernetes v1.18.0-rc.1 on Docker 19.03.6 ...
    ▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
    > kubelet.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
    > kubectl.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
    > kubeadm.sha256: 65 B / 65 B [--------------------------] 100.00% ? p/s 0s
    > kubeadm: 37.97 MiB / 37.97 MiB [--------------] 100.00% 435.33 MiB p/s 0s
    > kubectl: 41.99 MiB / 41.99 MiB [--------------] 100.00% 169.62 MiB p/s 1s
    > kubelet: 108.02 MiB / 108.02 MiB [------------] 100.00% 191.43 MiB p/s 1s
💣  Error starting cluster: init failed. output: "-- stdout --\n[init] Using Kubernetes version: v1.18.0-rc.1\n[pre
flight] Running pre-flight checks\n\n-- /stdout --\n** stderr ** \nW0323 22:03:58.134452   30219 configset.go:202] 
WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]\n
\t[WARNING IsDockerSystemdCheck]: detected \"cgroupfs\" as the Docker cgroup driver. The recommended driver is \"sy
stemd\". Please follow the guide at https://kubernetes.io/docs/setup/cri/\n\t[WARNING FileExisting-socat]: socat no
t found in system path\nerror execution phase preflight: [preflight] Some fatal errors occurred:\n\t[ERROR FileExis
ting-conntrack]: conntrack not found in system path\n[preflight] If you know what you are doing, you can make a che
ck non-fatal with `--ignore-preflight-errors=...`\nTo see the stack trace of this error execute with --v=5 or highe
r\n\n** /stderr **": /bin/bash -c "sudo mv /var/tmp/minikube/kubeadm.yaml.new /var/tmp/minikube/kubeadm.yaml && sud
o env PATH=/var/lib/minikube/binaries/v1.18.0-rc.1:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ig
nore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-m
inikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-ku
be-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernete
s-manifests-etcd.yaml,Port-10250,Swap,SystemVerification": exit status 1
stdout:
[init] Using Kubernetes version: v1.18.0-rc.1
[preflight] Running pre-flight checks
stderr:
W0323 22:03:58.134452   30219 configset.go:202] WARNING: kubeadm cannot validate component configs for API groups [
kubelet.config.k8s.io kubeproxy.config.k8s.io]
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is 
"systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING FileExisting-socat]: socat not found in system path
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR FileExisting-conntrack]: conntrack not found in system path
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
😿  minikube is exiting due to an error. If the above message is not useful, open an issue:
👉  https://github.com/kubernetes/minikube/issues/new/choose

This only happens with Kubernetes 1.18.0-rc.1 currently. I suspect it'll be the same for all versions going forward.

sudo apt install conntrack will successfully install conntrack on our integration test machines.

[ERROR FileExisting-conntrack]: conntrack not found in system path is the error to regex on for a nice solution message

kinfailing-test

Source