cloud:home
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
cloud:home [2017/02/14 16:20] djo created |
cloud:home [2017/04/12 18:55] (current) djo |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Currently this page is a set of random notes about using various cloud providers with/out Docker. | Currently this page is a set of random notes about using various cloud providers with/out Docker. | ||
| + | Here are some notes on [[cloud:why to consider developing on Windows|why to consider developing on Windows]]. | ||
| ===== Minikube on Windows 10 ===== | ===== Minikube on Windows 10 ===== | ||
| Notes: | Notes: | ||
| - | * Make sure Hyper-V is enabled (You need Windows 10 Pro) | + | * Make sure Hyper-V is enabled (You need Windows 10 Pro) |
| - | * Find the Hyper-V Manager and pin it somewhere; you'll need it. | + | * Find the Hyper-V Manager and pin it somewhere; you'll need it. |
| - | * Install Docker for Windows. | + | * Install Docker for Windows. |
| - | * Download the latest minikube.exe and kubectl.exe and put them on your path. | + | * Download the latest minikube.exe and kubectl.exe and put them on your path. |
| - | The first time I ran <code>minikube --vm-driver hyperv start</code> it failed with: | + | After that, I had to create two virtual switches, one for my hardwired Ethernet adapter and another for my Wifi adapter. Instructions are here: |
| - | <code> | + | https://docs.docker.com/machine/drivers/hyper-v/ |
| - | 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 | + | |
| - | + | ||
| - | <quote> | + | |
| - | Seen today on Windows 10, hyperv. Worked around by stopping and deleting the minikube VM in Hyper-V Manager, deleting ~/.minikube and trying again. | + | |
| - | </quote> | + | |
| ----- | ----- | ||
| - | Next steps: | + | Running the following as Administrator should now set up a Minikube cluster and open the dashboard in your default browser: |
| - | <code> | + | <code bash> |
| djo@oregano MINGW64 ~ | djo@oregano MINGW64 ~ | ||
| $ minikube config get vm-driver | $ minikube config get vm-driver | ||
| Line 43: | Line 36: | ||
| djo@oregano MINGW64 ~ | djo@oregano MINGW64 ~ | ||
| - | $ minikube start | + | $ minikube --hyperv-virtual-switch='Wireless Virtual Switch' start |
| Starting local Kubernetes cluster... | Starting local Kubernetes cluster... | ||
| - | .....hangs. | + | Kubectl is now configured to use the cluster. |
| + | |||
| + | djo@oregano MINGW64 ~ | ||
| + | $ minikube dashboard | ||
| + | Opening kubernetes dashboard in default browser... | ||
| </code> | </code> | ||
| - | hmmmmmm | + | |
| + | ===== Enabling Ingress in Minikube ===== | ||
| + | |||
| + | See: https://medium.com/@Oskarr3/setting-up-ingress-on-minikube-6ae825e98f82 | ||
| + | |||
| + | <code bash> | ||
| + | $ minikube addons enable ingress | ||
| + | </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. | ||
cloud/home.1487107237.txt.gz · Last modified: 2017/02/14 16:20 by djo
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
