I have an issue with "minikube start" on Mac machine - kubernetes

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.

Related

minikube failed to start

Hello so i was using yesterday minikube and it was working fine but today i was trying to start with minikube start command and it give the following errors :
and after running minikube status it give the following result :
Thanks in advance for any help.
You are getting the following error:
Exiting due to GUEST_START: Failed kubeconfig update: could not read config: Error decoding config from data control character are not allowed
and
getting k8s client: client config: error loading config file "C:\Users<Your User>/.kube/config control characters are not allowed
Those errors indicates that your $KUBECONFIG has an invalid character in it.
Troubleshooting
For the future use, please provide more detailed information. It's well described in Minikube Troubleshooting. The following commands might provide useful information for troubleshooting:
$ minikube logs
$ minikube start --alsologtostderr -v=2
$ kubectl config view
In minikube output there is also updating the running virtualbox "minikube" VM It might be related with network changes.
Possible Solution
Remove config file from C:\Users\<Your User>/.kube/ and start minikube again.
Update your Minikube to newest version (current is 1.16).
Recreate your minikube cluster using minikube delete and create new one.
Execite minikube update context.

Minikube won't start on mac

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

Minikube Start Error (Kubernetes) When Using hyperv Driver on Windows server 2016

I am trying to install Kubernetes on windows server 2016.
I tried to install minikube, and got some errors.
This is the tutorial that I followed:
https://www.assistanz.com/installing-minikube-on-windows-2016-server/
This is the command + error that I got:
PS C:\Windows\system32> minikube start –vm-driver=hyperv –hyperv-virtual-switch=Minikube
Starting local Kubernetes v1.10.0 cluster...
Starting VM... Downloading Minikube ISO
170.78 MB / 170.78 MB [============================================] 100.00% 0s
E1106 19:29:10.616564 11852 start.go:168] Error starting host: Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path.
Retrying.
E1106 19:29:10.689675 11852 start.go:174] Error starting host: Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
================================================================================
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]:
Someone knows how to solve it?
I googled it, but no luck.
Thanks!
I was never able to get the config parameters to work with minikube start.
I was able to get past this error using the minikube config commands in PowerShell (should also work at a command prompt):
minikube config set vm-driver hyperv
minikube config set hyperv-virtual-switch ExternalSwitch
minikube config view
minikube delete
minikube start
For more information on the command run: minikube config -h
Looking at the documentation you have provided, I have noticed that the screenshot shows a slight difference to the one they've quote.
I have also found this command in another piece of documentation from kubernetes here, showing the same command as that from the screenshot.
I suggest you try the following command;
minikube start --vm-driver=hyperv --hyperv-virtual-switch=Minikube
It is true that OP has pasted the incorrect command, because there is - instead of --. I tried to pass this arguments to minikube and all you get is an instant error. So the issue must be somewhere else. I remember having similar issue and it got resolved after deleting the .kube and .minikube folders and trying to run it again.
After taking a closer look this tutorial is destined for installation of minikube inside of a Windows Server 2016 Virtual Machine, so you have to have a Nested Virtualization able hardware:
Prerequisites The Hyper-V host and guest must both be Windows Server
2016/Windows 10 Anniversary Update or later. VM configuration version
8.0 or greater. An Intel processor with VT-x and EPT technology -- nesting is currently Intel-only. There are some differences with
virtual networking for second-level virtual machines. See "Nested
Virtual Machine Networking".
So the main question is, is that true in your scenario? Are you trying to perform your steps on Windows Server Hyper-V virtual machine with nested virtualization feature?
If you confirm that I have technical possibilities to check it in that scenario.
Otherwise I recommend using the "traditional way" of running minikube in Windows, according for example to this tutorial.

Get server misbehaving error when trying to build an image in Minikube on Windows 10

I have installed Minikube and am following the "Hello minikube" tutorial:
https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/#create-a-minikube-cluster
I have started minikube using the Hyperv driver:
minikube start --vm-driver="hyperv" --hyperv-virtual-switch="New Virtual Switch" --alsologtostderr
When I try to build an image using the Minikube Docker daemon, get the following error:
Step 1/4 : FROM node:6.9.2
Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 172.24.209.161:53: server misbehaving
What is going wrong here, and how can I fix it?
Here is some info about my environment:
minikube version: v0.23.0
OS: Windows 10 17_09
Try to clear all Docker data. This has done the job to me ;)
Try this if you can build your images on the local machine then take a copy of
/etc/resolv.conf
and copy the values and insert into the minikube cluster's /etc/resolv.conf using minikube ssh after all its just a VM and you are accessing the docker-engine/server using the environment variables..!!!
cheers :)

minikube start failed with ssh error

I got this error when start minikube. Can anybody help me? Thanks in advance.
I1105 12:57:36.987582 15567 cluster.go:77] Machine state: Running
Waiting for SSH to be available...
Getting to WaitForSSH function...
Using SSH client type: native
&{{{ 0 [] [] []} docker [0x83b300] 0x83b2b0 [] 0s} 127.0.0.1 22 }
About to run SSH command:
exit 0
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Error dialing TCP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
In order to have local instance of cluster-like Kubernetes installation there is minikube utility.
This tool can do all the magic of the installation process automatically.
In the short - the process of deploying consist of downloading runtime images, spinning up containers and configuring necessary elements of Kubernetes without any user interaction required. It works like a charm.
You may consider to just drop current installation and start it over?
Looks like
minikube delete && minikube start
may help.
Removing the .minikube file and starting minikube helps.
rm -rf ~/.minikube & minikube start