Update documentation without docker machine
parent
4f29ed6cd9
commit
c5bc38d2a0
|
|
@ -8,11 +8,7 @@ description: >
|
|||
|
||||
This document is written for contributors who are familiar with minikube, who would like to add support for a new VM driver.
|
||||
|
||||
minikube relies on docker-machine drivers to manage machines. This document discusses how to modify minikube, so that this driver may be used by `minikube start --driver=<new_driver>`.
|
||||
|
||||
## Creating a new driver
|
||||
|
||||
See [machine-drivers](https://github.com/machine-drivers) , the fork where all new docker-machine drivers are located.
|
||||
This document discusses how to modify minikube, so that this driver may be used by `minikube start --driver=<new_driver>`.
|
||||
|
||||
## Builtin vs External Drivers
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ aliases:
|
|||
---
|
||||
minikube can be deployed as a VM, a container, or bare-metal.
|
||||
|
||||
To do so, we use the [Docker Machine](https://github.com/docker/machine) library to provide a consistent way to interact with different environments. Here is what's supported:
|
||||
Here is what's supported:
|
||||
|
||||
## Linux
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue