Trying to start minikube on mac. Virtualization is being provided by VirtualBox.
$ minikube start
😄 minikube v1.1.0 on darwin (amd64)
🔥 Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
🐳 Configuring environment for Kubernetes v1.14.2 on Docker 18.09.6
❌ Unable to load cached images: loading cached images: loading image /Users/paul/.minikube/cache/images/k8s.gcr.io/kube-proxy_v1.14.2: Docker load /tmp/kube-proxy_v1.14.2: command failed: docker load -i /tmp/kube-proxy_v1.14.2
stdout:
stderr: open /var/lib/docker/image/overlay2/layerdb/tmp/write-set-542676317/diff: read-only file system
: Process exited with status 1
💣 Failed to setup certs: pre-copy: command failed: sudo rm -f /var/lib/minikube/certs/ca.crt
stdout:
stderr: rm: cannot remove '/var/lib/minikube/certs/ca.crt': Input/output error
: 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
Trying minikube delete followed by minikube start produces the same issue.
Docker is running and is signed in.
I also deleted all machines in virtualbox after minikube delete and still get the same result.
According to What if I answer a question in a comment? I am adding answer as well since many people dont read comments.
You can try to delete local config in MINIKUBE_HOME before starting minikube
rm -rf ~/.minikube
Try
minikube delete
and
minikube start
Related
I am trying to run minikube on ubuntu 18.04 version. getting an error while starting minikube. Please help. Tried minikube delete and start again but dosent work
Aspire-E5-573G:~$ minikube start --driver=podman --container-runtime=cri-o
😄 minikube v1.13.0 on Ubuntu 18.04
❗ Using podman 2 is not supported yet. your version is "2.0.6". minikube might not work. use at your own risk.
✨ Using the podman (experimental) driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
💾 Downloading Kubernetes v1.19.0 preload ...
> preloaded-images-k8s-v6-v1.19.0-cri-o-overlay-amd64.tar.lz4: 551.13 MiB /
🔄 Restarting existing podman container for "minikube" ...
🤦 StartHost failed, but will try again: podman inspect ip minikube: sudo -n podman container inspect -f {{.NetworkSettings.IPAddress}} minikube: exit status 125
stdout:
stderr:
Error: error inspecting object: no such container minikube
🔄 Restarting existing podman container for "minikube" ...
😿 Failed to start podman container. Running "minikube delete" may fix it: podman inspect ip minikube: sudo -n podman container inspect -f {{.NetworkSettings.IPAddress}} minikube: exit status 125
stdout:
stderr:
Error: error inspecting object: no such container minikube
❌ Exiting due to GUEST_PROVISION: Failed to start host: podman inspect ip minikube: sudo -n podman container inspect -f minikube: exit status 125
stdout:
stderr:
Error: error inspecting object: no such container minikube
😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose
As the error already indicates podman 2 is not yet supported.
Using podman 2 is not supported yet. your version is "2.0.6". minikube might not work. use at your own risk.
The workaround for this as described here is to use version v.1.9.3.
Here`s the merge that was done to warn about podman version 2.
Yes you are right. I tried using docker as the driver in the arguments and it worked. Podman 2 is not yet supported
I m trying to start minikube but it is showing as following
minikube start --vm-driver=virtualbox
🙄 minikube v1.5.2 on Darwin 10.13.6
💿 Downloading VM boot image ...
💣 Failed to cache ISO: https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso: invalid checksum: Error downloading checksum file: Get https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso.sha256: x509: certificate signed by unknown authority
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
kubectl version
Error in configuration:
* unable to read client-cert /Users/ashivan2/.minikube/client.crt for minikube due to open /Users/ashivan2/.minikube/client.crt: no such file or directory
* unable to read client-key /Users/ash/.minikube/client.key for minikube due to open /Users/ash/.minikube/client.key: no such file or directory
* unable to read certificate-authority /Users/ashivan2/.minikube/ca.crt for minikube due to open /Users/ash/.minikube/ca.crt: no such file or directory
minikube v1.5.2 on Darwin 10.13.6
💿 Downloading VM boot image ...
💣 Failed to cache ISO: https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso: invalid checksum: Error downloading checksum file: Get https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso.sha256: x509: certificate signed by unknown authority
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
minikube start -p minikube1 --vm-driver=virtualbox
[minikube1] minikube v1.5.2 on Darwin 10.13.6
💿 Downloading VM boot image ...
💣 Failed to cache ISO: https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso: invalid checksum: Error downloading checksum file: Get https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso.sha256: x509: certificate signed by unknown authority
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new/choose
I m trying to start minikube but it is showing as following and also I used minikube delete and minikube start but no use
I m expecting to start minikube in a fine way.
Can anyone help me out in solving the following issue
It appears that your machine does not have full access to the internet. Are you running minikube from China by any chance?
You can check by using curl to dowload the ISO: curl -LO https://storage.googleapis.com/minikube/iso/minikube-v1.5.1.iso
If you aren't able to use the internet, you can download the ISO file to ~/.minikube/cache/iso. You'll also need the appropriate docker images though, so I suggest running minikube start --download-only once from a machine with access to the internet, and copying ~/.minikube/cache over from there.
I am trying to start a local Kubernetes cluster using minikube start and getting the following error.
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0912 17:39:12.486830 17689 start.go:305] Error restarting
cluster: restarting kube-proxy: waiting for kube-proxy to be
up for configmap update: timed out waiting for the condition
Any idea how to ensure it starts? I am using VirtualBox and this tutorial. I tried the tip given here but without luck.
Also any specific reason why it takes so long to even reach to this stage? Or is it usually this slow?
following are the points to be remembered while starting minikube for such errors.
1) close the VirtualBox if opened.
2) delete the previous temp files generated.
3) if you are behind the proxy set the proxy.
4) then do the following...
$ minikube stop
$ minikube delete
$ minikube start
Below steps works for me :
Note : Do not work with root user
$ sudo minikube stop
$ sudo minikube delete
$ sudo rm -rf ~/.minikube
$ sudo minikube start --kubernetes-version=v1.12.4
you can specify any existing kubernetes version of your choice with prefix v compulsory
make sure .minikube directory created in users home directory but not in /root
I am able to build the minikube on alpine but facing issue while starting it.
Failed to start the minikube
/src/k8s.io/minikube # ./out/minikube-linux-amd64 start --vm-driver=none
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.10.0
Downloading kubelet v1.10.0
Finished Downloading kubelet v1.10.0
Finished Downloading kubeadm v1.10.0
E0712 16:31:44.365304 12423 start.go:258] Error updating cluster: starting kubelet: running command:
sudo systemctl daemon-reload &&
sudo systemctl enable kubelet &&
sudo systemctl start kubelet
: exit status 1
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:
The logs of minikube :
/src/k8s.io/minikube # ./out/minikube-linux-amd64 logs
2018/07/12 16:35:48 Error getting machine logs: getting cluster logs: running command: sudo journalctl -u kubelet
output: sudo: journalctl: command not found
: running command: sudo journalctl -u kubelet
.: exit status 1
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:
Any idea on how to start minikube on alpine?
Minikube was developed to start in the environment with systemd. You can try to use the official image of Ubuntu or other distribution of Linux with systemd inside. For using Minikube inside the Alpine, you may take this or this as an example for you.
While running the minikube start in windows 10, getting the following error.
Error : Error restarting cluster: restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition
Please help me resolve the give issue, I delete the minikube and restarted many time.
I faced the same issue on Centos 7
minikube delete
then
minikube start
solved my issue
I was getting the same error on mac os, tried almost everything but finally, this comment on GitHub saved my life :)
see steps
Now minikube has started as expected:
Below steps works for me :
Note : Do not work with root user
$ sudo minikube stop
$ sudo minikube delete
$ sudo rm -rf ~/.minikube
$ sudo minikube start --kubernetes-version=v1.12.4
you can specify any existing kubernetes version of your choice with prefix v compulsory
make sure .minikube directory created in users home directory but not in /root