{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/minikube/issues/2707","repository_url":"https://api.github.com/repos/kubernetes/minikube","labels_url":"https://api.github.com/repos/kubernetes/minikube/issues/2707/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/minikube/issues/2707/comments","events_url":"https://api.github.com/repos/kubernetes/minikube/issues/2707/events","html_url":"https://github.com/kubernetes/minikube/issues/2707","id":313276965,"node_id":"MDU6SXNzdWUzMTMyNzY5NjU=","number":2707,"title":"BUG - Minikube 0.26.0 - Ubuntu 17.10 - Unable to restart without error","user":{"login":"stephenpope","id":689099,"node_id":"MDQ6VXNlcjY4OTA5OQ==","avatar_url":"https://avatars2.githubusercontent.com/u/689099?v=4","gravatar_id":"","url":"https://api.github.com/users/stephenpope","html_url":"https://github.com/stephenpope","followers_url":"https://api.github.com/users/stephenpope/followers","following_url":"https://api.github.com/users/stephenpope/following{/other_user}","gists_url":"https://api.github.com/users/stephenpope/gists{/gist_id}","starred_url":"https://api.github.com/users/stephenpope/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stephenpope/subscriptions","organizations_url":"https://api.github.com/users/stephenpope/orgs","repos_url":"https://api.github.com/users/stephenpope/repos","events_url":"https://api.github.com/users/stephenpope/events{/privacy}","received_events_url":"https://api.github.com/users/stephenpope/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2018-04-11T11:07:30Z","updated_at":"2018-07-03T09:12:48Z","closed_at":null,"author_association":"NONE","body":"<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->\r\n\r\n**Is this a BUG REPORT**\r\n**Environment**: Ubuntu 17.10 x86_64\r\n\r\n**Minikube version**: v0.26.0\r\n- **OS** : 17.10 (Artful Aardvark)\r\n- **VM Driver** : None\r\n- **ISO version** : None\r\n- **Install tools**: None\r\n- **Others**:\r\n\r\n**What happened**:\r\n\r\nStarted minikube correctly .. \r\n```\r\nexport MINIKUBE_WANTUPDATENOTIFICATION=false\r\nexport MINIKUBE_WANTREPORTERRORPROMPT=false\r\nexport MINIKUBE_HOME=$HOME\r\nexport CHANGE_MINIKUBE_NONE_USER=true\r\nmkdir $HOME/.kube || true\r\ntouch $HOME/.kube/config\r\n\r\nexport KUBECONFIG=$HOME/.kube/config\r\n\r\nsudo -E minikube start --vm-driver=none\r\n\r\nStarting local Kubernetes v1.10.0 cluster...\r\nStarting VM...\r\nGetting VM IP address...\r\nMoving files into cluster...\r\nDownloading kubelet v1.10.0\r\nDownloading kubeadm v1.10.0\r\nFinished Downloading kubelet v1.10.0\r\nFinished Downloading kubeadm v1.10.0\r\nSetting up certs...\r\nConnecting to cluster...\r\nSetting up kubeconfig...\r\nStarting cluster components...\r\nKubectl is now configured to use the cluster.\r\n===================\r\nWARNING: IT IS RECOMMENDED NOT TO RUN THE NONE DRIVER ON PERSONAL WORKSTATIONS\r\n        The 'none' driver will run an insecure kubernetes apiserver as root that may leave the host vulnerable to CSRF attacks\r\n\r\nLoading cached images from config file.\r\n\r\nminikube: Running\r\ncluster: Running\r\nkubectl: Correctly Configured: pointing to minikube-vm at 172.27.162.20\r\n```\r\n.. stop minikube ..\r\n\r\n`sudo minikube stop`\r\n\r\n.. restart minikube (using same startup script to set env etc) ..\r\n\r\n```\r\nexport MINIKUBE_WANTUPDATENOTIFICATION=false\r\nexport MINIKUBE_WANTREPORTERRORPROMPT=false\r\nexport MINIKUBE_HOME=$HOME\r\nexport CHANGE_MINIKUBE_NONE_USER=true\r\nmkdir $HOME/.kube || true\r\ntouch $HOME/.kube/config\r\n\r\nexport KUBECONFIG=$HOME/.kube/config\r\n\r\nsudo -E minikube start --vm-driver=none\r\n\r\nmkdir: cannot create directory ‘/home/stp/.kube’: File exists\r\nStarting local Kubernetes v1.10.0 cluster...\r\nStarting VM...\r\nGetting VM IP address...\r\nMoving files into cluster...\r\nSetting up certs...\r\nConnecting to cluster...\r\nSetting up kubeconfig...\r\nStarting cluster components...\r\nE0411 09:14:33.070550   37677 start.go:276] Error starting cluster:  kubeadm init error sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap  running command: : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap\r\n output: [init] Using Kubernetes version: v1.10.0\r\n[init] Using Authorization modes: [Node RBAC]\r\n[preflight] Running pre-flight checks.\r\n        [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.03.0-ce. Max validated version: 17.03\r\n        [WARNING Hostname]: hostname \"minikube\" could not be reached\r\n        [WARNING Hostname]: hostname \"minikube\" lookup minikube on 127.0.0.53:53: server misbehaving\r\n        [WARNING FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists\r\n        [WARNING FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists\r\n        [WARNING FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists\r\n        [WARNING FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists\r\n        [WARNING Swap]: running with swap on is not supported. Please disable swap\r\n        [WARNING FileExisting-socat]: socat not found in system path\r\n        [WARNING FileExisting-crictl]: crictl not found in system path\r\nSuggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl\r\nFlag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.\r\n        [WARNING DirAvailable--data]: /data is not empty\r\n[preflight] Some fatal errors occurred:\r\n        [ERROR Port-10250]: Port 10250 is in use\r\n[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`\r\n: running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap\r\n.: exit status 2\r\n```\r\n\r\n**What you expected to happen**: System would start correctly.\r\n\r\n**Output of `minikube logs` (if applicable)**:\r\n\r\n**Anything else do we need to know**:\r\n\r\nTo `fix` / workaround : `rm -rf .kube` / `rm -rf /minikube` / `rm -rf /etc/kubernetes` (but that just allows me to start rather than re-start)\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/minikube/issues/comments/402068935","html_url":"https://github.com/kubernetes/minikube/issues/2707#issuecomment-402068935","issue_url":"https://api.github.com/repos/kubernetes/minikube/issues/2707","id":402068935,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMjA2ODkzNQ==","user":{"login":"wingman1960","id":8828771,"node_id":"MDQ6VXNlcjg4Mjg3NzE=","avatar_url":"https://avatars3.githubusercontent.com/u/8828771?v=4","gravatar_id":"","url":"https://api.github.com/users/wingman1960","html_url":"https://github.com/wingman1960","followers_url":"https://api.github.com/users/wingman1960/followers","following_url":"https://api.github.com/users/wingman1960/following{/other_user}","gists_url":"https://api.github.com/users/wingman1960/gists{/gist_id}","starred_url":"https://api.github.com/users/wingman1960/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wingman1960/subscriptions","organizations_url":"https://api.github.com/users/wingman1960/orgs","repos_url":"https://api.github.com/users/wingman1960/repos","events_url":"https://api.github.com/users/wingman1960/events{/privacy}","received_events_url":"https://api.github.com/users/wingman1960/received_events","type":"User","site_admin":false},"created_at":"2018-07-03T09:12:48Z","updated_at":"2018-07-03T09:12:48Z","author_association":"NONE","body":"Hi guys I found out the k8s dockers actually restarted even though it spawn error like         \r\n[ERROR Port-10250]: Port 10250 is in use\r\nin my case."}}
{"actor":{"display_login":"wingman1960"}}