update references to docker podman

site/content/en/_index.html

@@ -83,12 +83,14 @@ A single command away from reproducing your production environment, from the com
 {{% /blocks/feature %}}
 
 {{% blocks/feature icon="fa-thumbs-up" title="Cross-platform" %}}
-- Bare-metal
-- HyperKit
-- Hyper-V
 - KVM
+- Docker
+- HyperKit
+- Bare-metal
 - VirtualBox
+- Hyper-V
 - VMware
+- Podman
 {{% /blocks/feature %}}
 {{< /blocks/section >}}
 

site/content/en/docs/Contributing/triage.md

@@ -62,6 +62,7 @@ If the issue is specific to an operating system, hypervisor, container, addon, o
   - `co/kvm2`
   - `co/none-driver`
   - `co/docker-driver`
+  - `co/podman-driver`
   - `co/virtualbox`
 
 **co/[kubernetes component]**  - When the issue appears specific to a k8s component

site/content/en/docs/Reference/Drivers/includes/podman_usage.inc

@@ -1,7 +1,7 @@
 ## experimental
 
 This is an experimental driver. please use it only for experimental reasons.
-for a better kubernetes in container experience, use docker [driver](https://5e7c6ab90d754e000860cdfd--kubernetes-sigs-minikube.netlify.com/docs/reference/drivers/docker/).
+for a better kubernetes in container experience, use docker [driver](https://minikube.sigs.k8s.io/docs/reference/drivers/docker).
 
 ## Install Podman
 

site/content/en/docs/Reference/Drivers/podman.md

@@ -9,7 +9,7 @@ description: >
 
 ## Overview
 
-The podman driver is another kubernetes in container driver for minikube. simmilar to [docker](docs/reference/drivers/docker) driver.
+The podman driver is another kubernetes in container driver for minikube. simmilar to [docker](https://minikube.sigs.k8s.io/docs/reference/drivers/docker/) driver.
 podman driver is currently experimental. 
 and only supported on Linux and MacOs (with a remote podman server)
 

site/content/en/docs/Reference/disk_cache.md

@@ -4,7 +4,7 @@ linkTitle: "Disk cache"
 weight: 6
 date: 2019-08-01
 description: >
-  Cache Rules Everything Around Minikube
+  Cache Rules Everything Around minikube
 ---
 
 minikube has built-in support for caching downloaded resources into `$MINIKUBE_HOME/cache`. Here are the important file locations:

site/content/en/docs/Reference/persistent_volumes.md

@@ -7,7 +7,7 @@ description: >
   About persistent volumes (hostPath)
 ---
 
-minikube supports [PersistentVolumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) of type `hostPath` out of the box.  These PersistentVolumes are mapped to a directory inside the running Minikube instance (usually a VM, unless you use `--driver=none`, `--driver=docker`, or `--driver=podman`).  For more information on how this works, read the Dynamic Provisioning section below.
+minikube supports [PersistentVolumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) of type `hostPath` out of the box.  These PersistentVolumes are mapped to a directory inside the running minikube instance (usually a VM, unless you use `--driver=none`, `--driver=docker`, or `--driver=podman`).  For more information on how this works, read the Dynamic Provisioning section below.
 
 ## A note on mounts, persistence, and minikube hosts
 

site/content/en/docs/Tutorials/continuous_integration.md

@@ -9,13 +9,13 @@ description: >
 
 ## Overview
 
-Most continuous integration environments are already running inside a VM, and may not support nested virtualization. The `none` driver was designed for this use case.
+Most continuous integration environments are already running inside a VM, and may not support nested virtualization. The `none` driver was designed for this use case. or you could alternatively use the [Docker](https://minikube.sigs.k8s.io/docs/reference/drivers/docker).
 
 ## Prerequisites
 
 - VM running a systemd based Linux distribution
 
-## Tutorial
+## using none driver
 
  Here is an example, that runs minikube from a non-root user, and ensures that the latest stable kubectl is installed:
 
@@ -39,3 +39,7 @@ touch $KUBECONFIG
 
 sudo -E minikube start --driver=none
 ```
+
+##  Alternative ways
+
+you could alternatively use minikube's container drivers such as [Docker](https://minikube.sigs.k8s.io/docs/reference/drivers/docker) or [Podman](https://minikube.sigs.k8s.io/docs/reference/drivers/podman).

site/content/en/docs/Tutorials/nvidia_gpu.md

@@ -98,7 +98,7 @@ to expose GPUs with `--driver=kvm2`. Please don't mix these instructions.
 
 ## Why does minikube not support NVIDIA GPUs on macOS?
 
-VM drivers supported by minikube for macOS doesn't support GPU passthrough:
+drivers supported by minikube for macOS doesn't support GPU passthrough:
 
 - [mist64/xhyve#108](https://github.com/mist64/xhyve/issues/108)
 - [moby/hyperkit#159](https://github.com/moby/hyperkit/issues/159)

site/content/en/docs/Tutorials/untrusted_root_certificate.md

@@ -11,7 +11,7 @@ description: >
 
 Most organizations deploy their own Root Certificate and CA service inside the corporate networks.
 Internal websites, image repositories and other resources may install SSL server certificates issued by this CA service for security and privacy concerns.
-You may install the Root Certificate into the minikube VM to access these corporate resources within the cluster.
+You may install the Root Certificate into the minikube cluster to access these corporate resources within the cluster.
 
 ## Prerequisites
 
@@ -26,13 +26,13 @@ You may install the Root Certificate into the minikube VM to access these corpor
 openssl x509 -inform der -in my_company.cer -out my_company.pem
 ```
 
-* You may need to delete existing minikube VM
+* You may need to delete existing minikube cluster
 
 ```shell
 minikube delete
 ```
 
-* Copy the certificate before creating the minikube VM
+* Copy the certificate before creating the minikube cluster
 
 ```shell
 mkdir -p $HOME/.minikube/certs