Data in Motion

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== The Cloud and Docker ======

Currently this page is a set of random notes about using various cloud providers with/out Docker.


===== Minikube on Windows 10 =====

Notes:
   * Make sure Hyper-V is enabled (You need Windows 10 Pro)
   * Find the Hyper-V Manager and pin it somewhere; you'll need it.
   * Install Docker for Windows.
   * Download the latest minikube.exe and kubectl.exe and put them on your path.

After that, I had to create two virtual switches, one for my hardwired Ethernet adapter and another for my Wifi adapter.  Instructions are here:

https://docs.docker.com/machine/drivers/hyper-v/

-----

Running the following as Administrator should now set up a Minikube cluster and open the dashboard in your default browser:

<code>
djo@oregano MINGW64 ~
$ minikube config get vm-driver
specified key could not be found in config

djo@oregano MINGW64 ~
$ minikube config set vm-driver hyperv
These changes will take effect upon a minikube delete and then a minikube start

djo@oregano MINGW64 ~
$ minikube delete
Deleting local Kubernetes cluster...
Machine deleted.

djo@oregano MINGW64 ~
$ minikube --hyperv-virtual-switch='Wireless Virtual Switch' start
Starting local Kubernetes cluster...
Kubectl is now configured to use the cluster.

djo@oregano MINGW64 ~
$ minikube dashboard
Opening kubernetes dashboard in default browser...

</code>

===== Troubleshooting =====

1) The first time I ran <code>minikube --vm-driver hyperv start</code> it failed with:

<code>
Error updating localkube from asset: Error transferring localkube via ssh: Error running scp command: Process exited with: 1. Reason was:  ()
</code>

I found a workaround here: https://github.com/kubernetes/minikube/issues/817

> Seen today on Windows 10, hyperv. Worked around by stopping and deleting the minikube VM in Hyper-V Manager, deleting ~/.minikube and trying again.

I actually had to go into the Hyper-V Manager application and delete the VM that had been created.  Then I could run:

> rm -fr ~/.minikube


2) Forgetting to specify the virtual switch when starting minikube

First, you have to start minikube as Administrator.  If you don't have a command prompt open as Administrator, this is the time to do it.  Then you can

> minikube --hyperv-virtual-switch='Wireless Virtual Switch' start

where 'Wireless Virtual Switch' is whatever you named the active virtual switch.
Data in Motion

User Tools

Site Tools

Page Tools
