running command: : Process exited with status 2 #3491

liu-xuewen · 2018-12-23T12:03:08Z

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG

Please provide the following details:

Environment:

Minikube version (use minikube version):

OS (e.g. from /etc/os-release):
VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName):
ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
Install tools:
Others:
The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver:"; 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:
running command: : Process exited with status 2
What you expected to happen:
success
How to reproduce it (as minimally and precisely as possible):

Output of minikube logs (if applicable):

Anything else do we need to know:

The text was updated successfully, but these errors were encountered:

lnsyyj · 2018-12-23T18:15:56Z

macos same issues

yujiangdeMBP-13:~ yujiang$ rm -rf ~/.minikube/machines/minikube/
yujiangdeMBP-13:~ yujiang$ minikube start
Starting local Kubernetes v1.12.4 cluster...
Starting VM...
Downloading Minikube ISO
 178.88 MB / 178.88 MB [============================================] 100.00% 0s
Getting VM IP address...
E1224 01:32:46.938527    1227 start.go:211] Error parsing version semver:  Version string empty
Moving files into cluster...
Downloading kubelet v1.12.4
Downloading kubeadm v1.12.4
Finished Downloading kubeadm v1.12.4
Finished Downloading kubelet v1.12.4
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Stopping extra container runtimes...
Starting cluster components...
E1224 01:46:03.934313    1227 start.go:343] 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-minikube --ignore-preflight-errors=Port-10250 --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 --ignore-preflight-errors=CRI 
 running command: : Process exited with status 2

tvollmer · 2018-12-27T19:29:39Z

same on Windows 7 & git-bash; minikube status also displayed the apiserver as stopped.

resolution (for me) : jump off the corp network ( which monitors/intercepts ssl ), minikube delete && rm -rf ~/.minikube && rm -rf ~/.kube && minikube start

neurostream · 2018-12-28T01:03:20Z

Incorporating the observation by @tvollmer ( also behind MITM-style corp SSL proxy here ), was able to get a clean minikube start on MacOS.

I suppose this is because kubeadm pulls down its containers and other goodies it needs from the inner bootstrapping VM - which didn't have the same MITM corp proxy trust that my outer workstation terminal has ( which is why it gets past the initial "Downloading Minikube ISO" part)?

I'm still trying to get virtualbox and vmwarefusion to complete, but a minikube start with the hyperkit VM Driver is completing successfully for me now:

curl -kROL https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-hyperkit
sudo install -o root -g wheel -m 4755 docker-machine-driver-hyperkit /usr/local/bin/

minikube stop && minikube delete && rm -rf ~/.minikube && rm -rf ~/.kube
minikube cache delete
minikube start --vm-driver=hyperkit --bootstrapper=kubeadm

Mis2 · 2019-01-01T09:46:40Z

I am not on corp network, still running the same error. Minikube v0.32.0 in ubuntu 16.04.

mijklgps · 2019-01-02T03:06:26Z

minikube start

Starting local Kubernetes v1.12.4 cluster...
Starting VM...
Downloading Minikube ISO
178.88 MB / 178.88 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubelet v1.12.4
Downloading kubeadm v1.12.4
Finished Downloading kubeadm v1.12.4
Finished Downloading kubelet v1.12.4
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Stopping extra container runtimes...
Starting cluster components...
E0102 10:22:30.149014 47900 start.go:343] 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-minikube --ignore-preflight-errors=Port-10250 --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 --ignore-preflight-errors=CRI
running command: : Process exited with status 2

minikube logs

Version: v1.12.4
Jan 02 02:29:24 minikube kubelet[3594]: I0102 02:29:24.080004 3594 plugins.go:99] No cloud provider specified.
Jan 02 02:29:24 minikube kubelet[3594]: F0102 02:29:24.080072 3594 server.go:262] failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directory
Jan 02 02:29:24 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jan 02 02:29:24 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.

mpictor · 2019-01-06T22:29:47Z

Same on gentoo.

version

minikube version: v0.32.0

OS:
NAME=Gentoo
ID=gentoo
PRETTY_NAME="Gentoo/Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.gentoo.org/"
SUPPORT_URL="https://www.gentoo.org/support/"
BUG_REPORT_URL="https://bugs.gentoo.org/"

VM driver:
    "DriverName": "kvm2",

ISO version
        "Boot2DockerURL": "file:///home/mark/.minikube/cache/iso/minikube-v0.32.0.iso",
        "ISO": "/home/mark/.minikube/machines/minikube/boot2docker.iso",

output

$ minikube start --vm-driver kvm2

Starting local Kubernetes v1.12.4 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Stopping extra container runtimes...
Starting cluster components...
E0106 16:17:18.633063    1013 start.go:343] 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-minikube --ignore-preflight-errors=Port-10250 --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 --ignore-preflight-errors=CRI 
 running command: : Process exited with status 2

Logs

-- Logs begin at Sun 2019-01-06 22:27:48 UTC, end at Sun 2019-01-06 22:28:08 UTC. --
Jan 06 22:27:56 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --cluster-dns has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --client-ca-file has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --fail-swap-on has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --pod-manifest-path has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --allow-privileged has been deprecated, will be removed in a future version
Jan 06 22:27:56 minikube kubelet[2332]: Flag --cluster-domain has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:56 minikube kubelet[2332]: Flag --authorization-mode has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:27:57 minikube kubelet[2332]: I0106 22:27:57.783462    2332 server.go:408] Version: v1.12.4
Jan 06 22:27:57 minikube kubelet[2332]: I0106 22:27:57.783623    2332 plugins.go:99] No cloud provider specified.
Jan 06 22:27:57 minikube kubelet[2332]: F0106 22:27:57.783669    2332 server.go:262] failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directory
Jan 06 22:27:57 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jan 06 22:27:57 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.
Jan 06 22:28:07 minikube systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
Jan 06 22:28:07 minikube systemd[1]: kubelet.service: Scheduled restart job, restart counter is at 1.
Jan 06 22:28:07 minikube systemd[1]: Stopped kubelet: The Kubernetes Node Agent.
Jan 06 22:28:07 minikube systemd[1]: Started kubelet: The Kubernetes Node Agent.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --cluster-dns has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --client-ca-file has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --cgroup-driver has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --fail-swap-on has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --pod-manifest-path has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --allow-privileged has been deprecated, will be removed in a future version
Jan 06 22:28:07 minikube kubelet[2593]: Flag --cluster-domain has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: Flag --authorization-mode has been deprecated, This parameter should be set via the config file specified by the Kubelet's --config flag. See https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ for more information.
Jan 06 22:28:07 minikube kubelet[2593]: I0106 22:28:07.858905    2593 server.go:408] Version: v1.12.4
Jan 06 22:28:07 minikube kubelet[2593]: I0106 22:28:07.859289    2593 plugins.go:99] No cloud provider specified.
Jan 06 22:28:07 minikube kubelet[2593]: F0106 22:28:07.859383    2593 server.go:262] failed to run Kubelet: unable to load bootstrap kubeconfig: stat /etc/kubernetes/bootstrap-kubelet.conf: no such file or directory
Jan 06 22:28:07 minikube systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a
Jan 06 22:28:07 minikube systemd[1]: kubelet.service: Failed with result 'exit-code'.

Tianny · 2019-01-08T14:58:07Z

Same as I. How to resolve it ?

rahulguha · 2019-01-15T14:28:40Z

any resolution ?

tstromberg · 2019-01-19T00:38:57Z

minikube v0.33 does a slightly better job showing the reasons for kubeadm failures. Does someone mind retrying this on a newer release?

tstromberg · 2019-01-24T18:40:03Z

Also - I suspect this may be related to proxy/firewall issues. It's difficult to tell without additional logs from the person who opened this.

tstromberg · 2019-01-24T19:36:07Z

@liu-xuewen - do you mind attempting this with minikube v0.33.1, and attach the output of:

minikube logs

and:

minikube ssh 'docker logs $(docker ps -a -f name=k8s_kube-api --format={{.ID}})'

Thank you for the bug report!

fejta-bot · 2019-04-29T11:39:05Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

tstromberg · 2019-05-22T23:04:48Z

I'm closing this issue as it hasn't seen activity in awhile, and it's unclear if this issue still exists. If this issue does continue to exist in the most recent release of minikube, please feel free to re-open it.

Thank you for opening the issue!

tstromberg added co/kubeadm Issues relating to kubeadm ev/kubeadm-exited-status-2 kubeadm exited with status 2 labels Jan 23, 2019

tstromberg added triage/needs-information Indicates an issue needs more information in order to work on it. cause/firewall-or-proxy When firewalls or proxies seem to be interfering labels Jan 24, 2019

tstromberg added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Jan 24, 2019

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2019

tstromberg closed this as completed May 22, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

running command: : Process exited with status 2 #3491

running command: : Process exited with status 2 #3491

liu-xuewen commented Dec 23, 2018 •

edited

Loading

lnsyyj commented Dec 23, 2018 •

edited

Loading

tvollmer commented Dec 27, 2018 •

edited

Loading

neurostream commented Dec 28, 2018 •

edited

Loading

Mis2 commented Jan 1, 2019

mijklgps commented Jan 2, 2019

mpictor commented Jan 6, 2019

Tianny commented Jan 8, 2019

rahulguha commented Jan 15, 2019

tstromberg commented Jan 19, 2019

tstromberg commented Jan 24, 2019

tstromberg commented Jan 24, 2019

fejta-bot commented Apr 29, 2019

tstromberg commented May 22, 2019

running command: : Process exited with status 2 #3491

running command: : Process exited with status 2 #3491

Comments

liu-xuewen commented Dec 23, 2018 • edited Loading

lnsyyj commented Dec 23, 2018 • edited Loading

tvollmer commented Dec 27, 2018 • edited Loading

neurostream commented Dec 28, 2018 • edited Loading

Mis2 commented Jan 1, 2019

mijklgps commented Jan 2, 2019

minikube start

minikube logs

mpictor commented Jan 6, 2019

version

output

Logs

Tianny commented Jan 8, 2019

rahulguha commented Jan 15, 2019

tstromberg commented Jan 19, 2019

tstromberg commented Jan 24, 2019

tstromberg commented Jan 24, 2019

fejta-bot commented Apr 29, 2019

tstromberg commented May 22, 2019

liu-xuewen commented Dec 23, 2018 •

edited

Loading

lnsyyj commented Dec 23, 2018 •

edited

Loading

tvollmer commented Dec 27, 2018 •

edited

Loading

neurostream commented Dec 28, 2018 •

edited

Loading