Last active
October 27, 2021 09:21
-
-
Save bgalvao/f21a51f341f6eb855326229e8980cc68 to your computer and use it in GitHub Desktop.
Output of minikube start --kubernetes-version=v1.17.17 for an #94 opened in OpenMLOps https://github.com/datarevenue-berlin/OpenMLOps/issues/94
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| (base) [user@machinelmao openmlops]$ minikube start --kubernetes-version=v1.17.17 | |
| 😄 minikube v1.23.2 on Arch 21.1.6 | |
| ✨ Using the docker driver based on user configuration | |
| 👍 Starting control plane node minikube in cluster minikube | |
| 🚜 Pulling base image ... | |
| 🔥 Creating docker container (CPUs=2, Memory=3900MB) ... | |
| 🐳 Preparing Kubernetes v1.17.17 on Docker 20.10.8 ... | |
| ▪ Generating certificates and keys ... | |
| ▪ Booting up control plane ... | |
| 💢 initialization failed, will try again: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.17:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 1 | |
| stdout: | |
| [init] Using Kubernetes version: v1.17.17 | |
| [preflight] Running pre-flight checks | |
| [preflight] Pulling images required for setting up a Kubernetes cluster | |
| [preflight] This might take a minute or two, depending on the speed of your internet connection | |
| [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' | |
| [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" | |
| [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" | |
| [kubelet-start] Starting the kubelet | |
| [certs] Using certificateDir folder "/var/lib/minikube/certs" | |
| [certs] Using existing ca certificate authority | |
| [certs] Using existing apiserver certificate and key on disk | |
| [certs] Generating "apiserver-kubelet-client" certificate and key | |
| [certs] Generating "front-proxy-ca" certificate and key | |
| [certs] Generating "front-proxy-client" certificate and key | |
| [certs] Generating "etcd/ca" certificate and key | |
| [certs] Generating "etcd/server" certificate and key | |
| [certs] etcd/server serving cert is signed for DNS names [minikube localhost] and IPs [192.168.49.2 127.0.0.1 ::1] | |
| [certs] Generating "etcd/peer" certificate and key | |
| [certs] etcd/peer serving cert is signed for DNS names [minikube localhost] and IPs [192.168.49.2 127.0.0.1 ::1] | |
| [certs] Generating "etcd/healthcheck-client" certificate and key | |
| [certs] Generating "apiserver-etcd-client" certificate and key | |
| [certs] Generating "sa" key and public key | |
| [kubeconfig] Using kubeconfig folder "/etc/kubernetes" | |
| [kubeconfig] Writing "admin.conf" kubeconfig file | |
| [kubeconfig] Writing "kubelet.conf" kubeconfig file | |
| [kubeconfig] Writing "controller-manager.conf" kubeconfig file | |
| [kubeconfig] Writing "scheduler.conf" kubeconfig file | |
| [control-plane] Using manifest folder "/etc/kubernetes/manifests" | |
| [control-plane] Creating static Pod manifest for "kube-apiserver" | |
| [control-plane] Creating static Pod manifest for "kube-controller-manager" | |
| [control-plane] Creating static Pod manifest for "kube-scheduler" | |
| [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" | |
| [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s | |
| [kubelet-check] Initial timeout of 40s passed. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| Unfortunately, an error has occurred: | |
| timed out waiting for the condition | |
| This error is likely caused by: | |
| - The kubelet is not running | |
| - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) | |
| If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: | |
| - 'systemctl status kubelet' | |
| - 'journalctl -xeu kubelet' | |
| Additionally, a control plane component may have crashed or exited when started by the container runtime. | |
| To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker. | |
| Here is one example how you may list all Kubernetes containers running in docker: | |
| - 'docker ps -a | grep kube | grep -v pause' | |
| Once you have found the failing container, you can inspect its logs with: | |
| - 'docker logs CONTAINERID' | |
| stderr: | |
| W1027 08:15:44.151241 1659 validation.go:28] Cannot validate kube-proxy config - no validator is available | |
| W1027 08:15:44.151278 1659 validation.go:28] Cannot validate kubelet config - no validator is available | |
| [WARNING Swap]: running with swap on is not supported. Please disable swap | |
| [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.8. Latest validated version: 19.03 | |
| [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service' | |
| W1027 08:15:47.640068 1659 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| W1027 08:15:47.642705 1659 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster | |
| To see the stack trace of this error execute with --v=5 or higher | |
| ▪ Generating certificates and keys ... | |
| ▪ Booting up control plane ... | |
| 💣 Error starting cluster: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.17:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 1 | |
| stdout: | |
| [init] Using Kubernetes version: v1.17.17 | |
| [preflight] Running pre-flight checks | |
| [preflight] Pulling images required for setting up a Kubernetes cluster | |
| [preflight] This might take a minute or two, depending on the speed of your internet connection | |
| [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' | |
| [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" | |
| [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" | |
| [kubelet-start] Starting the kubelet | |
| [certs] Using certificateDir folder "/var/lib/minikube/certs" | |
| [certs] Using existing ca certificate authority | |
| [certs] Using existing apiserver certificate and key on disk | |
| [certs] Using existing apiserver-kubelet-client certificate and key on disk | |
| [certs] Using existing front-proxy-ca certificate authority | |
| [certs] Using existing front-proxy-client certificate and key on disk | |
| [certs] Using existing etcd/ca certificate authority | |
| [certs] Using existing etcd/server certificate and key on disk | |
| [certs] Using existing etcd/peer certificate and key on disk | |
| [certs] Using existing etcd/healthcheck-client certificate and key on disk | |
| [certs] Using existing apiserver-etcd-client certificate and key on disk | |
| [certs] Using the existing "sa" key | |
| [kubeconfig] Using kubeconfig folder "/etc/kubernetes" | |
| [kubeconfig] Writing "admin.conf" kubeconfig file | |
| [kubeconfig] Writing "kubelet.conf" kubeconfig file | |
| [kubeconfig] Writing "controller-manager.conf" kubeconfig file | |
| [kubeconfig] Writing "scheduler.conf" kubeconfig file | |
| [control-plane] Using manifest folder "/etc/kubernetes/manifests" | |
| [control-plane] Creating static Pod manifest for "kube-apiserver" | |
| [control-plane] Creating static Pod manifest for "kube-controller-manager" | |
| [control-plane] Creating static Pod manifest for "kube-scheduler" | |
| [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" | |
| [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s | |
| [kubelet-check] Initial timeout of 40s passed. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| Unfortunately, an error has occurred: | |
| timed out waiting for the condition | |
| This error is likely caused by: | |
| - The kubelet is not running | |
| - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) | |
| If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: | |
| - 'systemctl status kubelet' | |
| - 'journalctl -xeu kubelet' | |
| Additionally, a control plane component may have crashed or exited when started by the container runtime. | |
| To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker. | |
| Here is one example how you may list all Kubernetes containers running in docker: | |
| - 'docker ps -a | grep kube | grep -v pause' | |
| Once you have found the failing container, you can inspect its logs with: | |
| - 'docker logs CONTAINERID' | |
| stderr: | |
| W1027 08:17:43.247470 3899 validation.go:28] Cannot validate kube-proxy config - no validator is available | |
| W1027 08:17:43.247538 3899 validation.go:28] Cannot validate kubelet config - no validator is available | |
| [WARNING Swap]: running with swap on is not supported. Please disable swap | |
| [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.8. Latest validated version: 19.03 | |
| [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service' | |
| W1027 08:17:45.446702 3899 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| W1027 08:17:45.447722 3899 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster | |
| To see the stack trace of this error execute with --v=5 or higher | |
| ╭───────────────────────────────────────────────────────────────────────────────────────────╮ | |
| │ │ | |
| │ 😿 If the above advice does not help, please let us know: │ | |
| │ 👉 https://github.com/kubernetes/minikube/issues/new/choose │ | |
| │ │ | |
| │ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │ | |
| │ │ | |
| ╰───────────────────────────────────────────────────────────────────────────────────────────╯ | |
| ❌ Exiting due to K8S_KUBELET_NOT_RUNNING: wait: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.17.17:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,DirAvailable--var-lib-minikube-etcd,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 1 | |
| stdout: | |
| [init] Using Kubernetes version: v1.17.17 | |
| [preflight] Running pre-flight checks | |
| [preflight] Pulling images required for setting up a Kubernetes cluster | |
| [preflight] This might take a minute or two, depending on the speed of your internet connection | |
| [preflight] You can also perform this action in beforehand using 'kubeadm config images pull' | |
| [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env" | |
| [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml" | |
| [kubelet-start] Starting the kubelet | |
| [certs] Using certificateDir folder "/var/lib/minikube/certs" | |
| [certs] Using existing ca certificate authority | |
| [certs] Using existing apiserver certificate and key on disk | |
| [certs] Using existing apiserver-kubelet-client certificate and key on disk | |
| [certs] Using existing front-proxy-ca certificate authority | |
| [certs] Using existing front-proxy-client certificate and key on disk | |
| [certs] Using existing etcd/ca certificate authority | |
| [certs] Using existing etcd/server certificate and key on disk | |
| [certs] Using existing etcd/peer certificate and key on disk | |
| [certs] Using existing etcd/healthcheck-client certificate and key on disk | |
| [certs] Using existing apiserver-etcd-client certificate and key on disk | |
| [certs] Using the existing "sa" key | |
| [kubeconfig] Using kubeconfig folder "/etc/kubernetes" | |
| [kubeconfig] Writing "admin.conf" kubeconfig file | |
| [kubeconfig] Writing "kubelet.conf" kubeconfig file | |
| [kubeconfig] Writing "controller-manager.conf" kubeconfig file | |
| [kubeconfig] Writing "scheduler.conf" kubeconfig file | |
| [control-plane] Using manifest folder "/etc/kubernetes/manifests" | |
| [control-plane] Creating static Pod manifest for "kube-apiserver" | |
| [control-plane] Creating static Pod manifest for "kube-controller-manager" | |
| [control-plane] Creating static Pod manifest for "kube-scheduler" | |
| [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" | |
| [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s | |
| [kubelet-check] Initial timeout of 40s passed. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| [kubelet-check] It seems like the kubelet isn't running or healthy. | |
| [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused. | |
| Unfortunately, an error has occurred: | |
| timed out waiting for the condition | |
| This error is likely caused by: | |
| - The kubelet is not running | |
| - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) | |
| If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: | |
| - 'systemctl status kubelet' | |
| - 'journalctl -xeu kubelet' | |
| Additionally, a control plane component may have crashed or exited when started by the container runtime. | |
| To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker. | |
| Here is one example how you may list all Kubernetes containers running in docker: | |
| - 'docker ps -a | grep kube | grep -v pause' | |
| Once you have found the failing container, you can inspect its logs with: | |
| - 'docker logs CONTAINERID' | |
| stderr: | |
| W1027 08:17:43.247470 3899 validation.go:28] Cannot validate kube-proxy config - no validator is available | |
| W1027 08:17:43.247538 3899 validation.go:28] Cannot validate kubelet config - no validator is available | |
| [WARNING Swap]: running with swap on is not supported. Please disable swap | |
| [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.8. Latest validated version: 19.03 | |
| [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service' | |
| W1027 08:17:45.446702 3899 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| W1027 08:17:45.447722 3899 manifests.go:214] the default kube-apiserver authorization-mode is "Node,RBAC"; using "Node,RBAC" | |
| error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster | |
| To see the stack trace of this error execute with --v=5 or higher | |
| 💡 Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start | |
| 🍿 Related issue: https://github.com/kubernetes/minikube/issues/4172 | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment