none: Error restarting cluster: waiting for apiserver: apiserver process never appeared

[BaerSy]

My environment:

OS: Ubuntu 16.04 without VM installed

I run command:

minikube start --vm-driver=none --apiserver-ips 127.0.0.1 --apiserver-name localhost

Outputs:
minikube v1.4.0 on Ubuntu 16.04

• Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
• Starting existing none VM for "minikube" ...
• Waiting for the host to be provisioned ...
• Preparing Kubernetes v1.16.0 on Docker 18.09.7 ...
• Relaunching Kubernetes using kubeadm ...

X Error restarting cluster: waiting for apiserver: apiserver process never appeared
*

The output of the minikube logs command:

• ==> Docker <==
• -- Logs begin at Thu 2019-10-03 04:58:20 CST, end at Thu 2019-10-03 08:14:04 CST. --
• Oct 03 08:12:22 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:22.046441138+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:22 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:22.046486656+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:22 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:22.046522890+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:25 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:25.046437138+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:25 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:25.046479808+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:25 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:25.046514501+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:28 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:28.050409807+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:28 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:28.050448655+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:28 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:28.050475427+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:29 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:29.046570556+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:29 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:29.046604209+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:29 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:29.046629820+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:30 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:30.045819324+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:30 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:30.045851492+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:30 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:30.045876926+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:51 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:51.047773365+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:51 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:51.047806518+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:51 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:51.047833633+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:52.046694255+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:52.046728675+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:52.046761860+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:56 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:56.044425193+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:56 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:56.044454977+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:56 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:56.044480482+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.048005498+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.048038953+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.048067142+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.056056080+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.056080258+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:12:58 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:12:58.056099887+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:19 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:19.047045164+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:19 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:19.047080616+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:19 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:19.047105720+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:21 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:21.047332973+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:21 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:21.047365184+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:21 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:21.047391535+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:23 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:23.044341669+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:23 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:23.044375968+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:23 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:23.044408486+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:24 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:24.046795881+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:24 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:24.046830446+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:24 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:24.046857872+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:26 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:26.045905907+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:26 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:26.045940599+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:26 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:26.045967226+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:47 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:47.047377597+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:47 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:47.047409953+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:47 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:47.047446145+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.045285284+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.045328163+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.045355179+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.054405328+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.054428762+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:49 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:49.054447147+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.047562878+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.047594480+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.047620258+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.067817030+08:00" level=warning msg="Error getting v2 registry: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.067842730+08:00" level=info msg="Attempting next endpoint for pull after error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• Oct 03 08:13:52 ecs-de1e-0004 dockerd[25524]: time="2019-10-03T08:13:52.067865077+08:00" level=error msg="Handler for POST /images/create returned error: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
• ==> container status <==
• sudo: crictl: command not found
• CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
• ==> dmesg <==
• [Sep23 10:28] ACPI: RSDP 0x00000000000F6810 000014 (v00 BOCHS )
• [ +0.000000] ACPI: RSDT 0x00000000BFFE567E 000030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
• [ +0.000000] ACPI: FACP 0x00000000BFFE5432 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
• [ +0.000000] ACPI: DSDT 0x00000000BFFE0040 0053F2 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001)
• [ +0.000000] ACPI: FACS 0x00000000BFFE0000 000040
• [ +0.000000] ACPI: APIC 0x00000000BFFE54A6 0000B0 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
• [ +0.000000] ACPI: SRAT 0x00000000BFFE5556 000128 (v01 BOCHS BXPCSRAT 00000001 BXPC 00000001)
• [ +0.000000] ACPI: 1 ACPI AML tables successfully acquired and loaded
• [ +0.081174] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
• [ +0.000086] Support mounting host directories into pods #2
• [ +0.003473] Support kubernetes dashboard. #3
• [ +0.003402] Support creating a VM inside virtualbox on osx #4
• [ +0.003398] Multiple platform support #5
• [ +0.003467] Use GOVENDOREXPERIMENT=1 from the start #6
• [ +0.003399] Do not depend on localkube when released #7
• [ +0.028575] PCCT header not found.
• [ +0.026352] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
• [ +0.351589] ACPI: Enabled 3 GPEs in block 00 to 0F
• [ +0.125080] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
• [ +0.488518] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
• [ +0.065671] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
• [ +0.020269] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
• [ +2.619765] cgroup: new mount options do not match the existing superblock, will be ignored
• [Sep29 03:17] audit_printk_skb: 15 callbacks suppressed
• ==> kernel <==
• 08:14:04 up 9 days, 21:45, 1 user, load average: 0.04, 0.09, 0.07
• Linux ecs-de1e-0004 4.4.0-151-generic [Documentation] Readme.md should instruct how to install #178-Ubuntu SMP Tue Jun 11 08:30:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
• PRETTY_NAME="Ubuntu 16.04.6 LTS"
• ==> kubelet <==
• -- Logs begin at Thu 2019-10-03 04:58:20 CST, end at Thu 2019-10-03 08:14:04 CST. --
• Oct 03 08:14:01 ecs-de1e-0004 kubelet[16457]: E1003 08:14:01.945944 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.002265 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:450: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: I1003 08:14:02.025233 16457 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: I1003 08:14:02.025303 16457 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.046067 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.068501 16457 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: For verbose messaging see aws.Config.CredentialsChainVerboseErrors
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.069015 16457 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: For verbose messaging see aws.Config.CredentialsChainVerboseErrors
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.146205 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.201998 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.CSIDriver: Get https://localhost:8443/apis/storage.k8s.io/v1beta1/csidrivers?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.246345 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.346476 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.401860 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.RuntimeClass: Get https://localhost:8443/apis/node.k8s.io/v1beta1/runtimeclasses?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.446647 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.546765 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.602010 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.646901 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.655875 16457 controller.go:135] failed to ensure node lease exists, will retry in 7s, error: Get https://localhost:8443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/minikube?timeout=10s: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.747045 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.802748 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:459: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.847177 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:02 ecs-de1e-0004 kubelet[16457]: E1003 08:14:02.947322 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.003018 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:450: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: I1003 08:14:03.025188 16457 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.036130 16457 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: For verbose messaging see aws.Config.CredentialsChainVerboseErrors
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.047450 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.147575 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.202750 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.CSIDriver: Get https://localhost:8443/apis/storage.k8s.io/v1beta1/csidrivers?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.247706 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.347829 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.402490 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.RuntimeClass: Get https://localhost:8443/apis/node.k8s.io/v1beta1/runtimeclasses?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.447963 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.548094 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.602745 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.648220 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.748350 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.803428 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:459: Failed to list *v1.Node: Get https://localhost:8443/api/v1/nodes?fieldSelector=metadata.name%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.848471 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:03 ecs-de1e-0004 kubelet[16457]: E1003 08:14:03.948597 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.003776 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/kubelet.go:450: Failed to list *v1.Service: Get https://localhost:8443/api/v1/services?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: I1003 08:14:04.025179 16457 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.036160 16457 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: For verbose messaging see aws.Config.CredentialsChainVerboseErrors
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.048725 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.148837 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.203644 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.CSIDriver: Get https://localhost:8443/apis/storage.k8s.io/v1beta1/csidrivers?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.248978 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.349103 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.403182 16457 reflector.go:123] k8s.io/client-go/informers/factory.go:134: Failed to list *v1beta1.RuntimeClass: Get https://localhost:8443/apis/node.k8s.io/v1beta1/runtimeclasses?limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.449222 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.549353 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: I1003 08:14:04.599105 16457 kubelet_node_status.go:286] Setting node annotation to enable volume controller attach/detach
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.603397 16457 reflector.go:123] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://localhost:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dminikube&limit=500&resourceVersion=0: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: I1003 08:14:04.609449 16457 kubelet_node_status.go:72] Attempting to register node minikube
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.649495 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.749634 16457 kubelet.go:2267] node "minikube" not found
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.799015 16457 kubelet_node_status.go:94] Unable to register node "minikube" with API server: Post https://localhost:8443/api/v1/nodes: dial tcp [::1]:8443: connect: connection refused
• Oct 03 08:14:04 ecs-de1e-0004 kubelet[16457]: E1003 08:14:04.849770 16457 kubelet.go:2267] node "minikube" not found
  root@ecs-de1e-0004:~#

The operating system version: Ubuntu 16.04

[medyagh]

Thank you for creating this issue, I am curious of two things:

• has it ever worked and it stopped working ? if so do you mind trying minikube delete and try start again ?

• if it has never worked before (for none driver) could you try start with this additional flag
  minikube start --vm-driver=none --alsologtostderr -v=8

and I am also curious, does your machine have any special networking like vpn or firewalls or corp networking settings that affects the local network?

[BaerSy]

@medyagh it has never been worked. My server is normal cloud server, no vpn and firewall

I use "minikube delete", then

minikube start --vm-driver=none --alsologtostderr -v=8

The results as below:

root@ecs-de1e-0004:~# minikube start --vm-driver=none   --alsologtostderr -v=8
I1004 09:51:24.565004   27804 notify.go:125] Checking for updates...
I1004 09:51:24.884253   27804 start.go:236] hostinfo: {"hostname":"ecs-de1e-0004","uptime":948183,"bootTime":1569205701,"procs":237,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"16.04","kernelVersion":"4.4.0-151-generic","virtualizationSystem":"","virtualizationRole":"","hostid":"2b6963f8-8da7-4a4c-98f5-24ade4faebd1"}
I1004 09:51:24.884646   27804 start.go:246] virtualization:  
* minikube v1.4.0 on Ubuntu 16.04
I1004 09:51:24.885285   27804 profile.go:66] Saving config to /root/.minikube/profiles/minikube/config.json ...
I1004 09:51:24.885364   27804 lock.go:41] attempting to write to file "/root/.minikube/profiles/minikube/config.json" with filemode -rw-------
I1004 09:51:24.885508   27804 cluster.go:93] Machine does not exist... provisioning new machine
I1004 09:51:24.885523   27804 cluster.go:94] Provisioning machine with config: {KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.4.0.iso Memory:2000 CPUs:2 DiskSize:20000 VMDriver:none ContainerRuntime:docker HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.99.1/24 HypervVirtualSwitch: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false Downloader:{} DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true}
* Running on localhost (CPUs=8, Memory=16046MB, Disk=60346MB) ...
* OS release is Ubuntu 16.04.6 LTS
I1004 09:51:24.886817   27804 profile.go:66] Saving config to /root/.minikube/profiles/minikube/config.json ...
I1004 09:51:24.886858   27804 lock.go:41] attempting to write to file "/root/.minikube/profiles/minikube/config.json.tmp462119232" with filemode -rw-------
I1004 09:51:24.886977   27804 exec_runner.go:40] Run: sudo systemctl start docker
I1004 09:51:24.893074   27804 exec_runner.go:51] Run with output: docker version --format '{{.Server.Version}}'
* Preparing Kubernetes v1.16.0 on Docker 18.09.7 ...
I1004 09:51:24.922825   27804 settings.go:124] acquiring lock: {Name:kubeconfigUpdate Clock:{} Delay:10s Timeout:0s Cancel:}
I1004 09:51:24.922900   27804 settings.go:132] Updating kubeconfig:  /root/.kube/config
I1004 09:51:24.924192   27804 lock.go:41] attempting to write to file "/root/.kube/config" with filemode -rw-------
I1004 09:51:24.924603   27804 kubeadm.go:610] kubelet v1.16.0 config:
[Unit]
Wants=docker.socket
[Service]

ExecStart=

ExecStart=/var/lib/minikube/binaries/v1.16.0/kubelet --authorization-mode=Webhook --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --cgroup-driver=cgroupfs --client-ca-file=/var/lib/minikube/certs/ca.crt --cluster-dns=10.96.0.10 --cluster-domain=cluster.local --container-runtime=docker --fail-swap-on=false --hostname-override=minikube --kubeconfig=/etc/kubernetes/kubelet.conf --pod-manifest-path=/etc/kubernetes/manifests
[Install]

I1004 09:51:24.924635   27804 exec_runner.go:40] Run: pgrep kubelet && sudo systemctl stop kubelet

W1004 09:51:24.929235   27804 kubeadm.go:615] unable to stop kubelet: running command: pgrep kubelet && sudo systemctl stop kubelet: exit status 1

I1004 09:51:24.929419   27804 cache_binaries.go:63] Not caching binary, using https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubeadm

I1004 09:51:24.929437   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/cache/v1.16.0/kubeadm -> /var/lib/minikube/binaries/v1.16.0/kubeadm

I1004 09:51:24.929439   27804 cache_binaries.go:63] Not caching binary, using https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubelet

I1004 09:51:24.929547   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/cache/v1.16.0/kubelet -> /var/lib/minikube/binaries/v1.16.0/kubelet

I1004 09:51:25.016267   27804 exec_runner.go:40] Run: sudo systemctl daemon-reload && sudo systemctl start kubelet

I1004 09:51:25.144872   27804 certs.go:71] acquiring lock: {Name:setupCerts Clock:{} Delay:15s Timeout:0s Cancel:}

I1004 09:51:25.144972   27804 certs.go:79] Setting up /root/.minikube for IP: 192.168.1.26

I1004 09:51:25.145011   27804 crypto.go:69] Generating cert /root/.minikube/client.crt with IP's: []

I1004 09:51:25.147179   27804 crypto.go:157] Writing cert to /root/.minikube/client.crt ...

I1004 09:51:25.147198   27804 lock.go:41] attempting to write to file "/root/.minikube/client.crt" with filemode -rw-r--r--

I1004 09:51:25.147315   27804 crypto.go:165] Writing key to /root/.minikube/client.key ...

I1004 09:51:25.147328   27804 lock.go:41] attempting to write to file "/root/.minikube/client.key" with filemode -rw-------

I1004 09:51:25.147391   27804 crypto.go:69] Generating cert /root/.minikube/apiserver.crt with IP's: [192.168.1.26 10.96.0.1 10.0.0.1]

I1004 09:51:25.149494   27804 crypto.go:157] Writing cert to /root/.minikube/apiserver.crt ...

I1004 09:51:25.149517   27804 lock.go:41] attempting to write to file "/root/.minikube/apiserver.crt" with filemode -rw-r--r--

I1004 09:51:25.149611   27804 crypto.go:165] Writing key to /root/.minikube/apiserver.key ...

I1004 09:51:25.149629   27804 lock.go:41] attempting to write to file "/root/.minikube/apiserver.key" with filemode -rw-------

I1004 09:51:25.149695   27804 crypto.go:69] Generating cert /root/.minikube/proxy-client.crt with IP's: []

I1004 09:51:25.151744   27804 crypto.go:157] Writing cert to /root/.minikube/proxy-client.crt ...

I1004 09:51:25.151767   27804 lock.go:41] attempting to write to file "/root/.minikube/proxy-client.crt" with filemode -rw-r--r--

I1004 09:51:25.151888   27804 crypto.go:165] Writing key to /root/.minikube/proxy-client.key ...

I1004 09:51:25.151906   27804 lock.go:41] attempting to write to file "/root/.minikube/proxy-client.key" with filemode -rw-------

I1004 09:51:25.151980   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/ca.crt -> /var/lib/minikube/certs/ca.crt

I1004 09:51:25.151999   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/ca.key -> /var/lib/minikube/certs/ca.key

I1004 09:51:25.152013   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/apiserver.crt -> /var/lib/minikube/certs/apiserver.crt

I1004 09:51:25.152024   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/apiserver.key -> /var/lib/minikube/certs/apiserver.key

I1004 09:51:25.152038   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/proxy-client-ca.crt -> /var/lib/minikube/certs/proxy-client-ca.crt

I1004 09:51:25.152049   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/proxy-client-ca.key -> /var/lib/minikube/certs/proxy-client-ca.key

I1004 09:51:25.152063   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/proxy-client.crt -> /var/lib/minikube/certs/proxy-client.crt

I1004 09:51:25.152074   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/proxy-client.key -> /var/lib/minikube/certs/proxy-client.key

I1004 09:51:25.152165   27804 vm_assets.go:82] NewFileAsset: /root/.minikube/ca.crt -> /usr/share/ca-certificates/minikubeCA.pem

I1004 09:51:25.152765   27804 exec_runner.go:40] Run: which openssl

I1004 09:51:25.153985   27804 exec_runner.go:40] Run: sudo test -f '/etc/ssl/certs/minikubeCA.pem'

I1004 09:51:25.157711   27804 exec_runner.go:51] Run with output: openssl x509 -hash -noout -in '/usr/share/ca-certificates/minikubeCA.pem'

I1004 09:51:25.160437   27804 exec_runner.go:40] Run: sudo test -f '/etc/ssl/certs/b5213941.0'

Pulling images ...

I1004 09:51:25.164127   27804 exec_runner.go:40] Run: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml
Unable to pull images, which may be OK: running cmd: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml: running command: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm config images pull --config /var/tmp/minikube/kubeadm.yaml: exit status 1
Launching Kubernetes ...

I1004 09:51:40.243063   27804 kubeadm.go:232] StartCluster: {KubernetesVersion:v1.16.0 NodeIP:192.168.1.26 NodePort:8443 NodeName:minikube APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: ExtraOptions:[] ShouldLoadCachedImages:false EnableDefaultCNI:false}

I1004 09:51:40.243118   27804 exec_runner.go:51] Run with output: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

I1004 09:53:26.019152   27804 kubeadm.go:234] StartCluster complete in 1m45.77608924s

I1004 09:53:26.019188   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kube-apiserver" --format="{{.ID}}"

I1004 09:53:26.048544   27804 logs.go:160] 0 containers: []

W1004 09:53:26.048580   27804 logs.go:162] No container was found matching "kube-apiserver"

I1004 09:53:26.048598   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_coredns" --format="{{.ID}}"

I1004 09:53:26.076377   27804 logs.go:160] 0 containers: []

W1004 09:53:26.076408   27804 logs.go:162] No container was found matching "coredns"

I1004 09:53:26.076425   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kube-scheduler" --format="{{.ID}}"

I1004 09:53:26.104605   27804 logs.go:160] 0 containers: []

W1004 09:53:26.104636   27804 logs.go:162] No container was found matching "kube-scheduler"

I1004 09:53:26.104652   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kube-proxy" --format="{{.ID}}"

I1004 09:53:26.132969   27804 logs.go:160] 0 containers: []

W1004 09:53:26.132999   27804 logs.go:162] No container was found matching "kube-proxy"

I1004 09:53:26.133018   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kube-addon-manager" --format="{{.ID}}"

I1004 09:53:26.160807   27804 logs.go:160] 0 containers: []

W1004 09:53:26.160836   27804 logs.go:162] No container was found matching "kube-addon-manager"

I1004 09:53:26.160852   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kubernetes-dashboard" --format="{{.ID}}"

I1004 09:53:26.189081   27804 logs.go:160] 0 containers: []

W1004 09:53:26.189115   27804 logs.go:162] No container was found matching "kubernetes-dashboard"

I1004 09:53:26.189132   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_storage-provisioner" --format="{{.ID}}"

I1004 09:53:26.216472   27804 logs.go:160] 0 containers: []

W1004 09:53:26.216501   27804 logs.go:162] No container was found matching "storage-provisioner"

I1004 09:53:26.216518   27804 exec_runner.go:51] Run with output: docker ps -a --filter="name=k8s_kube-controller-manager" --format="{{.ID}}"

I1004 09:53:26.245312   27804 logs.go:160] 0 containers: []

W1004 09:53:26.245341   27804 logs.go:162] No container was found matching "kube-controller-manager"

I1004 09:53:26.245358   27804 logs.go:78] Gathering logs for kubelet ...

I1004 09:53:26.245371   27804 exec_runner.go:51] Run with output: journalctl -u kubelet -n 200

I1004 09:53:26.260188   27804 logs.go:78] Gathering logs for dmesg ...

I1004 09:53:26.260210   27804 exec_runner.go:51] Run with output: sudo dmesg -PH -L=never --level warn,err,crit,alert,emerg | tail -n 200

I1004 09:53:26.265826   27804 logs.go:78] Gathering logs for Docker ...

I1004 09:53:26.265843   27804 exec_runner.go:51] Run with output: sudo journalctl -u docker -n 200

I1004 09:53:26.285221   27804 logs.go:78] Gathering logs for container status ...

I1004 09:53:26.285244   27804 exec_runner.go:51] Run with output: sudo crictl ps -a || sudo docker ps -a

W1004 09:53:26.318099   27804 exit.go:101] Error starting cluster: cmd failed: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

: running command: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

output: [init] Using Kubernetes version: v1.16.0

[preflight] Running pre-flight checks

[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-ebtables]: ebtables not found in system path

[WARNING FileExisting-socat]: socat not found in system path

[WARNING Hostname]: hostname "minikube" could not be reached

[WARNING Hostname]: hostname "minikube": lookup minikube on 127.0.1.1:53: no such host

[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'

[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'

error execution phase preflight: [preflight] Some fatal errors occurred:

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.3.15-0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.6.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[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

: running command: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

.: exit status 1

*

X Error starting cluster: cmd failed: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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
: running command: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

output: [init] Using Kubernetes version: v1.16.0

[preflight] Running pre-flight checks

[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-ebtables]: ebtables not found in system path

[WARNING FileExisting-socat]: socat not found in system path

[WARNING Hostname]: hostname "minikube" could not be reached

[WARNING Hostname]: hostname "minikube": lookup minikube on 127.0.1.1:53: no such host

[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'

[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'

error execution phase preflight: [preflight] Some fatal errors occurred:

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-apiserver:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-controller-manager:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-scheduler:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/kube-proxy:v1.16.0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/pause:3.1: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/etcd:3.3.15-0: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[ERROR ImagePull]: failed to pull image k8s.gcr.io/coredns:1.6.2: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

, error: exit status 1

[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

: running command: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init --config /var/tmp/minikube/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--var-lib-minikube,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

.: exit status 1

*

Sorry that minikube crashed. If this was unexpected, we would love to hear from you:

https://github.com/kubernetes/minikube/issues/new/choose

root@ecs-de1e-0004:~#

[medyagh]

@BobOntario Thank you for updating the issue with more relevant information,

it seems like your vm does NOT have accerss to gcr (for example can not pull k8s.gcr.io/kube-apiserver:v1.16.0) ! we have had cases in corp networks or china they have to provide image-mirror options.

--image-repository string           Alternative image repository to pull docker images from. This can be used when you have limited access to gcr.io. Set it to "auto" to let minikube decide one for you. For Chinese mainland users, you may use local gcr.io mirrors such as registry.cn-hangzhou.aliyuncs.com/google_containers

do your company/network has a docker registry mirror ?

can you try inside your VM to see if you can do this manually and paste for me the output of this:

docker pull k8s.gcr.io/kube-apiserver:v1.16.0

[BaerSy]

@medyagh thanks for your kind help. Yes, you are right. It's images access problem. I added what you recommended and images can be accessed. But seems kube-apiserver not running as below logs:

ube@ecs-de1e-0004:~$ sudo minikube start --vm-driver=none  --alsologtostderr -v=8
I1007 04:34:08.529981   24613 notify.go:125] Checking for updates...
I1007 04:34:09.128323   24613 start.go:236] hostinfo: {"hostname":"ecs-de1e-0004","uptime":1188348,"bootTime":1569205701,"procs":246,"os":"linux","platform":"ubuntu","platformFamily":"debian","platformVersion":"16.04","kernelVersion":"4.4.0-151-generic","virtualizationSystem":"","virtualizationRole":"","hostid":"2b6963f8-8da7-4a4c-98f5-24ade4faebd1"}
I1007 04:34:09.128724   24613 start.go:246] virtualization:  
* minikube v1.4.0 on Ubuntu 16.04
I1007 04:34:09.129308   24613 profile.go:66] Saving config to /home/kube/.minikube/profiles/minikube/config.json ...
I1007 04:34:09.129367   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/profiles/minikube/config.json.tmp085091084" with filemode -rw-------
I1007 04:34:09.129629   24613 cluster.go:98] Skipping create...Using existing machine configuration
* Tip: Use 'minikube start -p <name>' to create a new cluster, or 'minikube delete' to delete this one.
I1007 04:34:09.129799   24613 none.go:257] checking for running kubelet ...
I1007 04:34:09.129811   24613 exec_runner.go:40] Run: systemctl is-active --quiet service kubelet
I1007 04:34:09.132582   24613 cluster.go:110] Machine state:  Running
* Using the running none "minikube" VM ...
I1007 04:34:09.132647   24613 cluster.go:128] engine options: &{ArbitraryFlags:[] DNS:[] GraphDir: Env:[] Ipv6:false InsecureRegistry:[10.96.0.0/12] Labels:[] LogLevel: StorageDriver: SelinuxEnabled:false TLSVerify:false RegistryMirror:[] InstallURL:https://get.docker.com}
* Waiting for the host to be provisioned ...
I1007 04:34:09.132680   24613 cluster.go:149] configureHost: &{BaseDriver:0xc00044b080 CommonDriver:<nil> URL:tcp://192.168.1.26:2376 runtime:0xc0006b2620 exec:0x2e05c10}
I1007 04:34:09.132704   24613 cluster.go:168] none is a local driver, skipping auth/time setup
I1007 04:34:09.132713   24613 cluster.go:151] configureHost completed within 33.117µs
I1007 04:34:09.132949   24613 profile.go:66] Saving config to /home/kube/.minikube/profiles/minikube/config.json ...
I1007 04:34:09.132988   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/profiles/minikube/config.json.tmp862046971" with filemode -rw-------
I1007 04:34:09.133134   24613 exec_runner.go:40] Run: sudo systemctl start docker
I1007 04:34:09.138851   24613 exec_runner.go:51] Run with output: docker version --format '{{.Server.Version}}'
* Preparing Kubernetes v1.16.0 on Docker 18.09.7 ...
I1007 04:34:09.169735   24613 settings.go:124] acquiring lock: {Name:kubeconfigUpdate Clock:{} Delay:10s Timeout:0s Cancel:<nil>}
I1007 04:34:09.169825   24613 settings.go:132] Updating kubeconfig:  /home/kube/.kube/config
I1007 04:34:09.171254   24613 lock.go:41] attempting to write to file "/home/kube/.kube/config" with filemode -rw-------
I1007 04:34:09.171758   24613 kubeadm.go:610] kubelet v1.16.0 config:
[Unit]
Wants=docker.socket

[Service]
ExecStart=
ExecStart=/var/lib/minikube/binaries/v1.16.0/kubelet --authorization-mode=Webhook --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --cgroup-driver=cgroupfs --client-ca-file=/var/lib/minikube/certs/ca.crt --cluster-dns=10.96.0.10 --cluster-domain=cluster.local --container-runtime=docker --fail-swap-on=false --hostname-override=minikube --kubeconfig=/etc/kubernetes/kubelet.conf --pod-manifest-path=/etc/kubernetes/manifests

[Install]
I1007 04:34:09.171783   24613 exec_runner.go:40] Run: pgrep kubelet && sudo systemctl stop kubelet
I1007 04:34:09.194538   24613 cache_binaries.go:63] Not caching binary, using https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubeadm
I1007 04:34:09.194567   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/cache/v1.16.0/kubeadm -> /var/lib/minikube/binaries/v1.16.0/kubeadm
I1007 04:34:09.194549   24613 cache_binaries.go:63] Not caching binary, using https://storage.googleapis.com/kubernetes-release/release/v1.16.0/bin/linux/amd64/kubelet
I1007 04:34:09.194661   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/cache/v1.16.0/kubelet -> /var/lib/minikube/binaries/v1.16.0/kubelet
I1007 04:34:09.290992   24613 exec_runner.go:40] Run: sudo systemctl daemon-reload && sudo systemctl start kubelet
I1007 04:34:13.657752   24613 certs.go:71] acquiring lock: {Name:setupCerts Clock:{} Delay:15s Timeout:0s Cancel:<nil>}
I1007 04:34:13.657881   24613 certs.go:79] Setting up /home/kube/.minikube for IP: 192.168.1.26
I1007 04:34:13.657927   24613 crypto.go:69] Generating cert /home/kube/.minikube/client.crt with IP's: []
I1007 04:34:13.660460   24613 crypto.go:157] Writing cert to /home/kube/.minikube/client.crt ...
I1007 04:34:13.660508   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/client.crt" with filemode -rw-r--r--
I1007 04:34:13.660787   24613 crypto.go:165] Writing key to /home/kube/.minikube/client.key ...
I1007 04:34:13.660807   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/client.key" with filemode -rw-------
I1007 04:34:13.660882   24613 crypto.go:69] Generating cert /home/kube/.minikube/apiserver.crt with IP's: [192.168.1.26 10.96.0.1 10.0.0.1]
I1007 04:34:13.663296   24613 crypto.go:157] Writing cert to /home/kube/.minikube/apiserver.crt ...
I1007 04:34:13.663322   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/apiserver.crt" with filemode -rw-r--r--
I1007 04:34:13.663436   24613 crypto.go:165] Writing key to /home/kube/.minikube/apiserver.key ...
I1007 04:34:13.663449   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/apiserver.key" with filemode -rw-------
I1007 04:34:13.663691   24613 crypto.go:69] Generating cert /home/kube/.minikube/proxy-client.crt with IP's: []
I1007 04:34:13.665742   24613 crypto.go:157] Writing cert to /home/kube/.minikube/proxy-client.crt ...
I1007 04:34:13.665766   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/proxy-client.crt" with filemode -rw-r--r--
I1007 04:34:13.665861   24613 crypto.go:165] Writing key to /home/kube/.minikube/proxy-client.key ...
I1007 04:34:13.665880   24613 lock.go:41] attempting to write to file "/home/kube/.minikube/proxy-client.key" with filemode -rw-------
I1007 04:34:13.665954   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/ca.crt -> /var/lib/minikube/certs/ca.crt
I1007 04:34:13.665975   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/ca.key -> /var/lib/minikube/certs/ca.key
I1007 04:34:13.665987   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/apiserver.crt -> /var/lib/minikube/certs/apiserver.crt
I1007 04:34:13.666001   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/apiserver.key -> /var/lib/minikube/certs/apiserver.key
I1007 04:34:13.666013   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/proxy-client-ca.crt -> /var/lib/minikube/certs/proxy-client-ca.crt
I1007 04:34:13.666030   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/proxy-client-ca.key -> /var/lib/minikube/certs/proxy-client-ca.key
I1007 04:34:13.666041   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/proxy-client.crt -> /var/lib/minikube/certs/proxy-client.crt
I1007 04:34:13.666051   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/proxy-client.key -> /var/lib/minikube/certs/proxy-client.key
I1007 04:34:13.666142   24613 vm_assets.go:82] NewFileAsset: /home/kube/.minikube/ca.crt -> /usr/share/ca-certificates/minikubeCA.pem
I1007 04:34:13.666781   24613 exec_runner.go:40] Run: which openssl
I1007 04:34:13.668234   24613 exec_runner.go:40] Run: sudo test -f '/etc/ssl/certs/minikubeCA.pem'
I1007 04:34:13.672394   24613 exec_runner.go:51] Run with output: openssl x509 -hash -noout -in '/usr/share/ca-certificates/minikubeCA.pem'
I1007 04:34:13.675175   24613 exec_runner.go:40] Run: sudo test -f '/etc/ssl/certs/b5213941.0'
* Relaunching Kubernetes using kubeadm ... 
I1007 04:34:13.679237   24613 kubeadm.go:396] RestartCluster start
I1007 04:34:13.679254   24613 exec_runner.go:40] Run: sudo test -d /data/minikube
I1007 04:34:13.683418   24613 kubeadm.go:216] /data/minikube check failed, skipping compat symlinks: running command: sudo test -d /data/minikube: exit status 1
I1007 04:34:13.683453   24613 exec_runner.go:40] Run: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init phase certs all --config /var/tmp/minikube/kubeadm.yaml
I1007 04:34:13.727332   24613 exec_runner.go:40] Run: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init phase kubeconfig all --config /var/tmp/minikube/kubeadm.yaml
I1007 04:34:14.547818   24613 exec_runner.go:40] Run: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init phase control-plane all --config /var/tmp/minikube/kubeadm.yaml
I1007 04:34:14.599256   24613 exec_runner.go:40] Run: sudo env PATH=/var/lib/minikube/binaries/v1.16.0:$PATH kubeadm init phase etcd local --config /var/tmp/minikube/kubeadm.yaml
I1007 04:34:14.647101   24613 kubeadm.go:454] Waiting for apiserver process ...
I1007 04:34:14.647134   24613 exec_runner.go:40] Run: sudo pgrep kube-apiserver
W1007 04:34:14.654832   24613 kubeadm.go:460] pgrep apiserver: running command: sudo pgrep kube-apiserver: exit status 1
I1007 04:34:14.955117   24613 exec_runner.go:40] Run: sudo pgrep kube-apiserver
W1007 04:34:14.964215   24613 kubeadm.go:460] pgrep apiserver: running command: sudo pgrep kube-apiserver: exit status 1
I1007 04:34:15.255180   24613 exec_runner.go:40] Run: sudo pgrep kube-apiserver
W1007 04:34:15.263153   24613 kubeadm.go:460] pgrep apiserver: running command: sudo pgrep kube-apiserver: exit status 1
I1007 04:34:15.555122   24613 exec_runner.go:40] Run: sudo pgrep kube-apiserver
W1007 04:34:15.562900   24613 kubeadm.go:460] pgrep apiserver: running command: sudo pgrep kube-apiserver: exit status 1
I1007 04:34:15.855145   24613 exec_runner.go:40] Run: sudo pgrep kube-apiserver

[medyagh]

@BobOntario glad that helped,

I suggested in minikube we do a better job, detecting the user access to the image repositories before we spin up ! and we let people know much earlier and much nicer that their connectivity to the image repository is restricted. and they need to pass options .

I would be happy to review any PR that does this

secondly, @BobOntario would minikube delete and start help ?

[jonathangiber]

Hi,
I run into a similar problem when building my packer image in circleci. The driver=none was working fine around 15 days ago and then started causing problems.

I'm attaching my logs:

==> eu-west-1: ! The 'none' driver provides limited isolation and may reduce system security and reliability.
eu-west-1: *
==> eu-west-1: ! For more information, see:
==> eu-west-1: I1010 10:44:29.732917 24385 kubeadm.go:454] Waiting for apiserver process ...
==> eu-west-1: I1010 10:44:29.732925 24385 exec_runner.go:40] Run: sudo pgrep kube-apiserver
==> eu-west-1: I1010 10:44:29.742964 24385 kubeadm.go:469] Waiting for apiserver to port healthy status ...
==> eu-west-1: I1010 10:44:29.748135 24385 kubeadm.go:156] https://:8443/healthz response: &{Status:200 OK StatusCode:200 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Cache-Control:[no-cache, private] Content-Length:[2] Content-Type:[text/plain; charset=utf-8] Date:[Thu, 10 Oct 2019 10:44:29 GMT] X-Content-Type-Options:[nosniff]] Body:0xc000850880 ContentLength:2 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc0000bce00 TLS:0xc0000cc2c0}
==> eu-west-1: I1010 10:44:29.748199 24385 kubeadm.go:472] apiserver status: Running, err:
==> eu-west-1: I1010 10:44:29.748207 24385 kubeadm.go:451] duration metric: took 15.291195ms to wait for apiserver status ...
==> eu-west-1: I1010 10:44:29.748792 24385 kapi.go:58] client config for minikube: &rest.Config{Host:"https://:8443", APIPath:"", ContentConfig:rest.ContentConfig{AcceptContentTypes:"", ContentType:"", GroupVersion:(*schema.GroupVersion)(nil), NegotiatedSerializer:runtime.NegotiatedSerializer(nil)}, Username:"", Password:"", BearerToken:"", BearerTokenFile:"", Impersonate:rest.ImpersonationConfig{UserName:"", Groups:[]string(nil), Extra:map[string][]string(nil)}, AuthProvider:, AuthConfigPersister:rest.AuthProviderConfigPersister(nil), ExecProvider:, TLSClientConfig:rest.sanitizedTLSClientConfig{Insecure:false, ServerName:"", CertFile:"/home/ubuntu/.minikube/client.crt", KeyFile:"/home/ubuntu/.minikube/client.key", CAFile:"/home/ubuntu/.minikube/ca.crt", CertData:[]uint8(nil), KeyData:[]uint8(nil), CAData:[]uint8(nil)}, UserAgent:"", Transport:http.RoundTripper(nil), WrapTransport:(transport.WrapperFunc)(0x159bb40), QPS:0, Burst:0, RateLimiter:flowcontrol.RateLimiter(nil), Timeout:0, Dial:(func(context.Context, string, string) (net.Conn, error))(nil)}
==> eu-west-1: I1010 10:44:29.750841 24385 kapi.go:74] Waiting for pod with label "kube-system" in ns "k8s-app=kube-proxy" ...
==> eu-west-1: I1010 10:44:29.758814 24385 kapi.go:85] Found 0 Pods for label selector k8s-app=kube-proxy
==> eu-west-1: I1010 10:44:35.262891 24385 kapi.go:85] Found 1 Pods for label selector k8s-app=kube-proxy
==> eu-west-1: I1010 10:44:35.262913 24385 kapi.go:95] waiting for pod "k8s-app=kube-proxy", current state: Pending: []
==> eu-west-1: I1010 10:44:35.775862 24385 kapi.go:107] duration metric: took 6.025015963s to wait for k8s-app=kube-proxy ...
==> eu-west-1: I1010 10:44:35.775902 24385 kapi.go:74] Waiting for pod with label "kube-system" in ns "component=etcd" ...
==> eu-west-1: I1010 10:44:35.808130 24385 kapi.go:85] Found 0 Pods for label selector component=etcd
==> eu-west-1: I1010 10:45:48.811149 24385 kapi.go:85] Found 1 Pods for label selector component=etcd
==> eu-west-1: I1010 10:45:48.811172 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:49.311110 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:49.811108 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:50.311072 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:50.811392 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:51.311436 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:51.811208 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:52.312302 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:52.811035 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:53.311007 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:53.811110 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:54.311023 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:54.811257 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:55.311800 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:55.811088 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:56.311017 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:56.811076 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:57.311154 24385 kapi.go:95] waiting for pod "component=etcd", current state: Pending: []
==> eu-west-1: I1010 10:45:57.811266 24385 kapi.go:107] duration metric: took 1m22.035357176s to wait for component=etcd ...
==> eu-west-1: I1010 10:45:57.811307 24385 kapi.go:74] Waiting for pod with label "kube-system" in ns "component=kube-scheduler" ...
==> eu-west-1: I1010 10:45:57.813494 24385 kapi.go:85] Found 1 Pods for label selector component=kube-scheduler
==> eu-west-1: I1010 10:45:57.813513 24385 kapi.go:107] duration metric: took 2.206198ms to wait for component=kube-scheduler ...
==> eu-west-1: I1010 10:45:57.813530 24385 kapi.go:74] Waiting for pod with label "kube-system" in ns "component=kube-controller-manager" ...
==> eu-west-1: I1010 10:45:57.815491 24385 kapi.go:85] Found 1 Pods for label selector component=kube-controller-manager
==> eu-west-1: I1010 10:45:57.815509 24385 kapi.go:107] duration metric: took 1.977772ms to wait for component=kube-controller-manager ...
eu-west-1: * Waiting for: apiserver proxy etcd scheduler controller dns
==> eu-west-1: I1010 10:45:57.815524 24385 kapi.go:74] Waiting for pod with label "kube-system" in ns "k8s-app=kube-dns" ...
==> eu-west-1: I1010 10:45:57.817902 24385 kapi.go:85] Found 2 Pods for label selector k8s-app=kube-dns
eu-west-1: * Done! kubectl is now configured to use "minikube"
==> eu-west-1: I1010 10:45:57.817972 24385 kapi.go:107] duration metric: took 2.444895ms to wait for k8s-app=kube-dns ...
eu-west-1: * For best results, install kubectl: https://kubernetes.io/docs/tasks/tools/install-kubectl/
==> eu-west-1: Terminating the source AWS instance...
==> eu-west-1: Cleaning up any extra volumes...
==> eu-west-1: No volumes to clean up, skipping
==> eu-west-1: Deleting temporary security group...
Build 'eu-west-1' errored: Script exited with non-zero exit status: 70.Allowed exit codes are: [0]

[BaerSy]

@medyagh thanks . Followed your instructions and I switched to Ubuntu 18.04 from 16.04. Now it works with below messages:

Waiting for: apiserver proxy etcd scheduler controller dns
Done! kubectl is now configured to use "minikube"_

I tried to see dashboard with the following command:

http://server_ip:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

I got the following response, not sure what's wrong?

{
"kind": "Status",
"apiVersion": "v1",
"metadata": {

},
"status": "Failure",
"message": "services "kubernetes-dashboard" not found",
"reason": "NotFound",
"details": {
"name": "kubernetes-dashboard",
"kind": "services"
},
"code": 404
}

[BaerSy]

I also found the following outputs when i applied "http://server_IP:8001.

{
"paths": [
"/api",
"/api/v1",
"/apis",
"/apis/",
"/apis/admissionregistration.k8s.io",
"/apis/admissionregistration.k8s.io/v1",
"/apis/admissionregistration.k8s.io/v1beta1",
"/apis/apiextensions.k8s.io",
"/apis/apiextensions.k8s.io/v1",
"/apis/apiextensions.k8s.io/v1beta1",
"/apis/apiregistration.k8s.io",
"/apis/apiregistration.k8s.io/v1",
"/apis/apiregistration.k8s.io/v1beta1",
"/apis/apps",
"/apis/apps/v1",
"/apis/authentication.k8s.io",
"/apis/authentication.k8s.io/v1",
"/apis/authentication.k8s.io/v1beta1",
"/apis/authorization.k8s.io",
"/apis/authorization.k8s.io/v1",
"/apis/authorization.k8s.io/v1beta1",
"/apis/autoscaling",
"/apis/autoscaling/v1",
"/apis/autoscaling/v2beta1",
"/apis/autoscaling/v2beta2",
"/apis/batch",
"/apis/batch/v1",
"/apis/batch/v1beta1",
"/apis/certificates.k8s.io",
"/apis/certificates.k8s.io/v1beta1",
"/apis/coordination.k8s.io",
"/apis/coordination.k8s.io/v1",
"/apis/coordination.k8s.io/v1beta1",
"/apis/events.k8s.io",
"/apis/events.k8s.io/v1beta1",
"/apis/extensions",
"/apis/extensions/v1beta1",
"/apis/networking.k8s.io",
"/apis/networking.k8s.io/v1",
"/apis/networking.k8s.io/v1beta1",
"/apis/node.k8s.io",
"/apis/node.k8s.io/v1beta1",
"/apis/policy",
"/apis/policy/v1beta1",
"/apis/rbac.authorization.k8s.io",
"/apis/rbac.authorization.k8s.io/v1",
"/apis/rbac.authorization.k8s.io/v1beta1",
"/apis/scheduling.k8s.io",
"/apis/scheduling.k8s.io/v1",
"/apis/scheduling.k8s.io/v1beta1",
"/apis/storage.k8s.io",
"/apis/storage.k8s.io/v1",
"/apis/storage.k8s.io/v1beta1",
"/healthz",
"/healthz/autoregister-completion",
"/healthz/etcd",
"/healthz/log",
"/healthz/ping",
"/healthz/poststarthook/apiservice-openapi-controller",
"/healthz/poststarthook/apiservice-registration-controller",
"/healthz/poststarthook/apiservice-status-available-controller",
"/healthz/poststarthook/bootstrap-controller",
"/healthz/poststarthook/ca-registration",
"/healthz/poststarthook/crd-informer-synced",
"/healthz/poststarthook/generic-apiserver-start-informers",
"/healthz/poststarthook/kube-apiserver-autoregistration",
"/healthz/poststarthook/rbac/bootstrap-roles",
"/healthz/poststarthook/scheduling/bootstrap-system-priority-classes",
"/healthz/poststarthook/start-apiextensions-controllers",
"/healthz/poststarthook/start-apiextensions-informers",
"/healthz/poststarthook/start-kube-aggregator-informers",
"/healthz/poststarthook/start-kube-apiserver-admission-initializer",
"/livez",
"/livez/autoregister-completion",
"/livez/log",
"/livez/ping",
"/livez/poststarthook/apiservice-openapi-controller",
"/livez/poststarthook/apiservice-registration-controller",
"/livez/poststarthook/apiservice-status-available-controller",
"/livez/poststarthook/bootstrap-controller",
"/livez/poststarthook/ca-registration",
"/livez/poststarthook/crd-informer-synced",
"/livez/poststarthook/generic-apiserver-start-informers",
"/livez/poststarthook/kube-apiserver-autoregistration",
"/livez/poststarthook/rbac/bootstrap-roles",
"/livez/poststarthook/scheduling/bootstrap-system-priority-classes",
"/livez/poststarthook/start-apiextensions-controllers",
"/livez/poststarthook/start-apiextensions-informers",
"/livez/poststarthook/start-kube-aggregator-informers",
"/livez/poststarthook/start-kube-apiserver-admission-initializer",
"/logs",
"/metrics",
"/openapi/v2",
"/readyz",
"/readyz/autoregister-completion",
"/readyz/log",
"/readyz/ping",
"/readyz/poststarthook/apiservice-openapi-controller",
"/readyz/poststarthook/apiservice-registration-controller",
"/readyz/poststarthook/apiservice-status-available-controller",
"/readyz/poststarthook/bootstrap-controller",
"/readyz/poststarthook/ca-registration",
"/readyz/poststarthook/crd-informer-synced",
"/readyz/poststarthook/generic-apiserver-start-informers",
"/readyz/poststarthook/kube-apiserver-autoregistration",
"/readyz/poststarthook/rbac/bootstrap-roles",
"/readyz/poststarthook/scheduling/bootstrap-system-priority-classes",
"/readyz/poststarthook/start-apiextensions-controllers",
"/readyz/poststarthook/start-apiextensions-informers",
"/readyz/poststarthook/start-kube-aggregator-informers",
"/readyz/poststarthook/start-kube-apiserver-admission-initializer",
"/readyz/shutdown",
"/version"
]
}

[tstromberg]

@medyagh thanks . Followed your instructions and I switched to Ubuntu 18.04 from 16.04. Now it works with below messages:

Waiting for: apiserver proxy etcd scheduler controller dns Done! kubectl is now configured to use "minikube"_

I tried to see dashboard with the following command:

http://server_ip:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

I got the following response, not sure what's wrong?

{
"kind": "Status",
"apiVersion": "v1",
"metadata": {

},
"status": "Failure",
"message": "services "kubernetes-dashboard" not found",
"reason": "NotFound",
"details": {
"name": "kubernetes-dashboard",
"kind": "services"
},
"code": 404
}

You may need to start the dashboard?

[tstromberg]

I'm glad this got sorted.

minikube v1.5.0-beta.0 now does a connectivity check with the image repository, which should clarify the issue some.

[pravanjan]

@medyagh it has never been worked. My server is normal cloud server, no vpn and firewall

I use "minikube delete", then

minikube start --vm-driver=none --alsologtostderr -v=8

The results as below:

I had a similar issue on my Mac this worked for me.
I use "minikube delete", then
minikube start --alsologtostderr -v=8

[OmarLaham]

For me, this solution solved the problem: https://github.com/kubernetes/minikube/issues/4172#issuecomment-1267069635

[vistait2018]

i checked for downloaded images in docker , i got this gcr.io/k8s-minikube/kicbase and deleted them .Working from windows. From the command prompt docker rmi "imageid" then minkube delete and minkube start .My issue was cause by poor networkwork.