minikube fails to start kubernetes-version v1.6.0

Created on 14 Jul 2019 · 7Comments · Source: kubernetes/minikube

[root@node-1 ~]# minikube start --memory 8000 --cpus 2 --kubernetes-version v1.6.0
😄  minikube v1.2.0 on linux (amd64)
⚠️  Please don't run minikube as root or with 'sudo' privileges. It isn't necessary.
💿  Downloading Minikube ISO ...
 129.33 MB / 129.33 MB [============================================] 100.00% 0s
🔥  Creating virtualbox VM (CPUs=2, Memory=8000MB, Disk=20000MB) ...
🐳  Configuring environment for Kubernetes v1.6.0 on Docker 18.09.6
💾  Downloading kubeadm v1.6.0
💾  Downloading kubelet v1.6.0
🚜  Pulling images ...
❌  Unable to pull images, which may be OK: pull command is not supported by kubeadm v1.6.0
🚀  Launching Kubernetes ... 

💣  Error starting cluster: cmd failed: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--data-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,SystemVerification
Error: unknown flag: --ignore-preflight-errors
Usage:
  kubeadm init [flags]

Flags:
      --apiserver-advertise-address string      The IP address the API Server will advertise it's listening on. 0.0.0.0 means the default network interface's address.
      --apiserver-bind-port int32               Port for the API Server to bind to (default 6443)
      --apiserver-cert-extra-sans stringSlice   Optional extra altnames to use for the API Server serving cert. Can be both IP addresses and dns names.
      --cert-dir string                         The path where to save and store the certificates (default "/etc/kubernetes/pki")
      --config string                           Path to kubeadm config file (WARNING: Usage of a configuration file is experimental)
      --kubernetes-version string               Choose a specific Kubernetes version for the control plane (default "v1.6.0")
      --pod-network-cidr string                 Specify range of IP addresses for the pod network; if set, the control plane will automatically allocate CIDRs for every node
      --service-cidr string                     Use alternative range of IP address for service VIPs (default "10.96.0.0/12")
      --service-dns-domain string               Use alternative domain for services, e.g. "myorg.internal" (default "cluster.local")
      --skip-preflight-checks                   Skip preflight checks normally run before modifying the system
      --token string                            The token to use for establishing bidirectional trust between nodes and masters.
      --token-ttl duration                      The duration before the bootstrap token is automatically deleted. 0 means 'never expires'.


: Process exited with status 1

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new
❌  Problems detected in "kubelet":
    Jul 14 07:48:32 minikube kubelet[2761]: unknown flag: --bootstrap-kubeconfig

Version details

[root@node-1 ~]# minikube version
minikube version: v1.2.0
[root@node-1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 (Maipo)

arekubernetes-versions triagunresolved

Source

sbuvaneshkumar

Most helpful comment

As suggested by @tstromberg the problem was fixed by running minukube delete.
Thanks for your prompt reply, you guys rock!

ragagit on 19 Jul 2019

👍2

All 7 comments

The oldest supported Kubernetes version is v1.10

afbjorklund on 14 Jul 2019

I have a similar problem

Screen Shot 2019-07-14 at 3 51 34 PM

ragagit on 14 Jul 2019

@ragagit : your problem doesn't look similar (kubernetes v1.15.0), please open a new issue

afbjorklund on 15 Jul 2019

v1.6.0 is not supported. Admittedly, we can do a better job with the error message though. See #4673

https://github.com/kubernetes/minikube/blob/master/docs/configuring_kubernetes.md#selecting-a-kubernetes-version

The other failure you had seems unrelated. Please run minikube delete to erase the old v1.6 VM, and if the problem occurs again, open a new issue. Thank you for your issue report!