Updated drivers.md for info on Hyper-V machines using dynamic memory management
parent
f32754f2a9
commit
25e7a18d6f
|
@ -54,3 +54,5 @@ $ sudo chmod u+s $(brew --prefix)/opt/docker-machine-driver-xhyve/bin/docker-mac
|
|||
#### HyperV driver
|
||||
|
||||
Hyper-v users may need to create a new external network switch as described [here](https://docs.docker.com/machine/drivers/hyper-v/). This step may prevent a problem in which `minikube start` hangs indefinitely, unable to ssh into the minikube virtual machine. In this add, add the `--hyperv-virtual-switch=switch-name` argument to the `minikube start` command.
|
||||
|
||||
On some machines, having **dynamic memory management** turned on for the minikube VM can cause problems of unexpected and random restrarts which manifests itself in simply losing the connetion to the cluster, after which `minikube status` would simply state `localkube stopped`. Machine restarts are caused due to following Hyper-V error: `The dynamic memory balancer could not add memory to the virtual machine 'minikube' because its configured maximum has been reached`. **Solution**: turned the dynamic memory management in hyper-v settings off (and allocate a fixed amount of memory to the machine).
|
||||
|
|
Loading…
Reference in New Issue