minikube failed to start #19505
Comments
|
D:\Projects\Kubernetes>minikube start --driver docker --alsologtostderr
I0826 08:26:20.950085 10996 ubuntu.go:169] provisioning hostname "minikube" I0826 08:26:21.552433 10996 cli_runner.go:164] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube I0826 08:26:21.975811 10996 main.go:141] libmachine: SSH cmd err, output: : I0826 08:26:23.383765 10996 ubuntu.go:71] root file system type: overlay [Service] This file is a systemd drop-in unit that inherits from the base dockerd configuration.The base configuration already specifies an 'ExecStart=...' command. The first directivehere is to clear out that command inherited from the base configuration. Without this,the command from the base configuration and the command specified here are treated asa sequence of commands, which is not the desired behavior, nor is it valid -- systemdwill catch this invalid input and refuse to start the service with an error like:Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.NOTE: default-ulimit=nofile is set to an arbitrary number for consistency with othercontainer runtimes. If left unlimited, it may result in OOM issues with MySQL.ExecStart= Having non-zero Limit*s causes performance problems due to accounting overheadin the kernel. We recommend using cgroups to do container-local accounting.LimitNOFILE=infinity Uncomment TasksMax if your systemd version supports it.Only systemd 226 and above support this version.TasksMax=infinity set delegate yes so that systemd does not reset the cgroups of docker containersDelegate=yes kill only the docker process, not all processes in the cgroupKillMode=process [Install] [Service] This file is a systemd drop-in unit that inherits from the base dockerd configuration.The base configuration already specifies an 'ExecStart=...' command. The first directivehere is to clear out that command inherited from the base configuration. Without this,the command from the base configuration and the command specified here are treated asa sequence of commands, which is not the desired behavior, nor is it valid -- systemdwill catch this invalid input and refuse to start the service with an error like:Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.NOTE: default-ulimit=nofile is set to an arbitrary number for consistency with othercontainer runtimes. If left unlimited, it may result in OOM issues with MySQL.ExecStart= Having non-zero Limit*s causes performance problems due to accounting overheadin the kernel. We recommend using cgroups to do container-local accounting.LimitNOFILE=infinity Uncomment TasksMax if your systemd version supports it.Only systemd 226 and above support this version.TasksMax=infinity set delegate yes so that systemd does not reset the cgroups of docker containersDelegate=yes kill only the docker process, not all processes in the cgroupKillMode=process [Install] I0826 08:26:23.812350 10996 cli_runner.go:164] Run: docker container inspect -f "'{{(index (index .NetworkSettings.Ports "22/tcp") 0).HostPort}}'" minikube stderr:
-- /stdout -- -- /stdout -- [Service] [Install]
apiVersion: kubeadm.k8s.io/v1beta3
|
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
and others
What Happened?
D:\Projects\Kubernetes>minikube start --driver docker
E0826 07:57:18.861912 7804 start.go:812] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
E0826 07:57:19.001177 7804 start.go:812] api.Load failed for minikube: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
! Executing "docker ps -a --format {{.Names}}" took an unusually long time: 3.2065878s
! StartHost failed, but will try again: creating host: create host timed out in 360.000000 seconds
! initialization failed, will try again: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.30.0:$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,NumCPU,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3
stdout:
stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
To see the stack trace of this error execute with --v=5 or higher
X Error starting cluster: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.30.0:$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,NumCPU,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3
stdout:
stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
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.txtand attach logs.txt to the GitHub issue. ││ │
╰─────────────────────────────────────────────────────────────────────────────────────────────╯
X Exiting due to K8S_INVALID_CERT_HOSTNAME: wait: /bin/bash -c "sudo env PATH="/var/lib/minikube/binaries/v1.30.0:$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,NumCPU,Mem,SystemVerification,FileContent--proc-sys-net-bridge-bridge-nf-call-iptables": Process exited with status 3
stdout:
stderr:
apiServer.certSANs: Invalid value: "": altname is not a valid IP address, DNS label or a DNS label with subdomain wildcards: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)'); a wildcard DNS-1123 subdomain must start with '.', followed by a valid DNS subdomain, which must consist of lower case alphanumeric characters, '-' or '.' and end with an alphanumeric character (e.g. '.example.com', regex used for validation is '*.a-z0-9?(.a-z0-9?)')
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.txtand attach logs.txt to the GitHub issue. ││ │
Attach the log file
logs.txt
Operating System
None
Driver
None
The text was updated successfully, but these errors were encountered: