add docs for docker driver
parent
095ccbe562
commit
1c8d580682
|
@ -4,28 +4,19 @@ linkTitle: "docker"
|
||||||
weight: 3
|
weight: 3
|
||||||
date: 2020-02-05
|
date: 2020-02-05
|
||||||
description: >
|
description: >
|
||||||
Docker driver (EXPERIMENTAL)
|
Docker driver
|
||||||
---
|
---
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
The Docker driver is an experimental VM-free driver that ships with minikube v1.7.
|
The Docker driver is a VM-free driver.
|
||||||
|
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/docker_usage.inc" %}}
|
||||||
|
|
||||||
This driver was inspired by the [kind project](https://kind.sigs.k8s.io/), and uses a modified version of its base image.
|
|
||||||
|
|
||||||
## Special features
|
## Special features
|
||||||
|
|
||||||
No hypervisor required when run on Linux.
|
- Cross platform (linux, macos, windows)
|
||||||
|
- No hypervisor required when run on Linux.
|
||||||
|
|
||||||
## Limitations
|
|
||||||
|
|
||||||
As an experimental driver, not all commands are supported on all platforms. Notably: `mount,` `service`, `tunnel`, and others. Most of these limitations will be addressed by minikube v1.8 (March 2020)
|
|
||||||
|
|
||||||
## Issues
|
|
||||||
|
|
||||||
* [Full list of open 'kic-driver' issues](https://github.com/kubernetes/minikube/labels/co%2Fkic-driver)
|
|
||||||
|
|
||||||
## Troubleshooting
|
|
||||||
|
|
||||||
* Run `minikube start --alsologtostderr -v=1` to debug crashes
|
|
||||||
* If your docker is too slow on mac os try [Improving docker performance](https://docs.docker.com/docker-for-mac/osxfs-caching/)
|
|
||||||
|
|
|
@ -7,7 +7,6 @@ date: 2018-08-05
|
||||||
description: >
|
description: >
|
||||||
Microsoft Hyper-V driver
|
Microsoft Hyper-V driver
|
||||||
---
|
---
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
Hyper-V is a native hypervisor built in to modern versions of Microsoft Windows.
|
Hyper-V is a native hypervisor built in to modern versions of Microsoft Windows.
|
||||||
|
|
|
@ -0,0 +1,7 @@
|
||||||
|
To use baremetal driver (none driver). verify that your operating system is Linux and also have 'systemd' installed.
|
||||||
|
|
||||||
|
```shell
|
||||||
|
pidof systemd && echo "yes" || echo "no"
|
||||||
|
```
|
||||||
|
If the above command outputs "no":
|
||||||
|
Your system is not suitable for none driver.
|
|
@ -0,0 +1,9 @@
|
||||||
|
To use container drivers, verify that your system has either have 'docker' or 'podman' installed.
|
||||||
|
```shell
|
||||||
|
docker version
|
||||||
|
```
|
||||||
|
or
|
||||||
|
|
||||||
|
```shell
|
||||||
|
podman version
|
||||||
|
```
|
|
@ -0,0 +1,11 @@
|
||||||
|
To use VM drivers, verify that your system has virtualization support enabled:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
egrep -q 'vmx|svm' /proc/cpuinfo && echo yes || echo no
|
||||||
|
```
|
||||||
|
|
||||||
|
If the above command outputs "no":
|
||||||
|
|
||||||
|
- If you are running within a VM, your hypervisor does not allow nested virtualization. You will need to use the *None (bare-metal)* driver
|
||||||
|
- If you are running on a physical machine, ensure that your BIOS has hardware virtualization enabled
|
||||||
|
|
|
@ -0,0 +1,19 @@
|
||||||
|
To check if virtualization is supported, run the following command on your Windows terminal or command prompt.
|
||||||
|
|
||||||
|
```shell
|
||||||
|
systeminfo
|
||||||
|
```
|
||||||
|
If you see the following output, virtualization is supported:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
|
||||||
|
Virtualization Enabled In Firmware: Yes
|
||||||
|
Second Level Address Translation: Yes
|
||||||
|
Data Execution Prevention Available: Yes
|
||||||
|
```
|
||||||
|
|
||||||
|
If you see the following output, your system already has a Hypervisor installed and you can skip the next step.
|
||||||
|
|
||||||
|
```shell
|
||||||
|
Hyper-V Requirements: A hypervisor has been detected.
|
||||||
|
```
|
|
@ -0,0 +1,16 @@
|
||||||
|
## Install Docker
|
||||||
|
|
||||||
|
- [Docker Desktop](https://hub.docker.com/search?q=&type=edition&offering=community&sort=updated_at&order=desc)
|
||||||
|
|
||||||
|
## Usage
|
||||||
|
|
||||||
|
Start a cluster using the docker driver:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
minikube start --driver=docker
|
||||||
|
```
|
||||||
|
To make docker the default driver:
|
||||||
|
|
||||||
|
```shell
|
||||||
|
minikube config set driver docker
|
||||||
|
```
|
|
@ -8,12 +8,17 @@ description: >
|
||||||
Linux KVM (Kernel-based Virtual Machine) driver
|
Linux KVM (Kernel-based Virtual Machine) driver
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
[KVM (Kernel-based Virtual Machine)](https://www.linux-kvm.org/page/Main_Page) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions. To work with KVM, minikube uses the [libvirt virtualization API](https://libvirt.org/)
|
[KVM (Kernel-based Virtual Machine)](https://www.linux-kvm.org/page/Main_Page) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions. To work with KVM, minikube uses the [libvirt virtualization API](https://libvirt.org/)
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/kvm2_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/kvm2_usage.inc" %}}
|
||||||
|
|
||||||
|
## Check virtualization support
|
||||||
|
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/virtualization_check_linux.inc" %}}
|
||||||
|
|
||||||
## Special features
|
## Special features
|
||||||
|
|
||||||
The `minikube start` command supports 3 additional kvm specific flags:
|
The `minikube start` command supports 3 additional kvm specific flags:
|
||||||
|
|
|
@ -39,28 +39,32 @@ curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-{{< la
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% /tabs %}}
|
{{% /tabs %}}
|
||||||
|
|
||||||
## Hypervisor Setup
|
## Driver Setup
|
||||||
|
|
||||||
Verify that your system has virtualization support enabled:
|
|
||||||
|
|
||||||
```shell
|
|
||||||
egrep -q 'vmx|svm' /proc/cpuinfo && echo yes || echo no
|
|
||||||
```
|
|
||||||
|
|
||||||
If the above command outputs "no":
|
|
||||||
|
|
||||||
- If you are running within a VM, your hypervisor does not allow nested virtualization. You will need to use the *None (bare-metal)* driver
|
|
||||||
- If you are running on a physical machine, ensure that your BIOS has hardware virtualization enabled
|
|
||||||
|
|
||||||
{{% tabs %}}
|
{{% tabs %}}
|
||||||
|
{{% tab "Docker" %}}
|
||||||
|
## Check container support
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_container.inc" %}}
|
||||||
|
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/docker_usage.inc" %}}
|
||||||
|
{{% /tab %}}
|
||||||
|
|
||||||
{{% tab "KVM" %}}
|
{{% tab "KVM" %}}
|
||||||
|
## Check virtualization support
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_virtualization_linux.inc" %}}
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/kvm2_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/kvm2_usage.inc" %}}
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% tab "VirtualBox" %}}
|
{{% tab "VirtualBox" %}}
|
||||||
|
## Check virtualization support
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_virtualization_linux.inc" %}}
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/virtualbox_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/virtualbox_usage.inc" %}}
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% tab "None (bare-metal)" %}}
|
{{% tab "None (bare-metal)" %}}
|
||||||
|
## Check baremetal support
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_baremetal_linux.inc" %}}
|
||||||
|
|
||||||
If you are already running minikube from inside a VM, it is possible to skip the creation of an additional VM layer by using the `none` driver.
|
If you are already running minikube from inside a VM, it is possible to skip the creation of an additional VM layer by using the `none` driver.
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/none_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/none_usage.inc" %}}
|
||||||
|
|
|
@ -50,6 +50,9 @@ brew upgrade minikube
|
||||||
## Hypervisor Setup
|
## Hypervisor Setup
|
||||||
|
|
||||||
{{% tabs %}}
|
{{% tabs %}}
|
||||||
|
{{% tab "Docker" %}}
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/docker_usage.inc" %}}
|
||||||
|
{{% /tab %}}
|
||||||
{{% tab "Hyperkit" %}}
|
{{% tab "Hyperkit" %}}
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/hyperkit_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/hyperkit_usage.inc" %}}
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
|
|
|
@ -7,8 +7,6 @@ weight: 3
|
||||||
### Prerequisites
|
### Prerequisites
|
||||||
|
|
||||||
* Windows 8 or above
|
* Windows 8 or above
|
||||||
* A hypervisor, such as Hyper-V or VirtualBox
|
|
||||||
* Hardware virtualization support must be enabled in BIOS
|
|
||||||
* 4GB of RAM
|
* 4GB of RAM
|
||||||
|
|
||||||
### Installation
|
### Installation
|
||||||
|
@ -30,33 +28,23 @@ After it has installed, close the current CLI session and reopen it. minikube sh
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% /tabs %}}
|
{{% /tabs %}}
|
||||||
|
|
||||||
## Hypervisor Setup
|
|
||||||
|
|
||||||
To check if virtualization is supported, run the following command on your Windows terminal or command prompt.
|
|
||||||
|
|
||||||
```shell
|
|
||||||
systeminfo
|
|
||||||
```
|
|
||||||
If you see the following output, virtualization is supported:
|
|
||||||
|
|
||||||
```shell
|
|
||||||
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
|
|
||||||
Virtualization Enabled In Firmware: Yes
|
|
||||||
Second Level Address Translation: Yes
|
|
||||||
Data Execution Prevention Available: Yes
|
|
||||||
```
|
|
||||||
|
|
||||||
If you see the following output, your system already has a Hypervisor installed and you can skip the next step.
|
|
||||||
|
|
||||||
```shell
|
|
||||||
Hyper-V Requirements: A hypervisor has been detected.
|
|
||||||
```
|
|
||||||
|
|
||||||
{{% tabs %}}
|
{{% tabs %}}
|
||||||
|
{{% tab "Docker" %}}
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/docker_usage.inc" %}}
|
||||||
|
{{% /tab %}}
|
||||||
|
|
||||||
{{% tab "Hyper-V" %}}
|
{{% tab "Hyper-V" %}}
|
||||||
|
## Check Hypervisor
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_virtualization_windows.inc" %}}
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/hyperv_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/hyperv_usage.inc" %}}
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% tab "VirtualBox" %}}
|
{{% tab "VirtualBox" %}}
|
||||||
|
## Check Hypervisor
|
||||||
|
{{% readfile file="/docs/Reference/Drivers/includes/check_virtualization_windows.inc" %}}
|
||||||
|
|
||||||
{{% readfile file="/docs/Reference/Drivers/includes/virtualbox_usage.inc" %}}
|
{{% readfile file="/docs/Reference/Drivers/includes/virtualbox_usage.inc" %}}
|
||||||
{{% /tab %}}
|
{{% /tab %}}
|
||||||
{{% /tabs %}}
|
{{% /tabs %}}
|
||||||
|
|
Loading…
Reference in New Issue