From 45dd7d107abba2f79a523224eb0f4af973604aca Mon Sep 17 00:00:00 2001
From: Trishank Karthik Kuppusamy
 <33133073+trishankatdatadog@users.noreply.github.com>
Date: Wed, 29 Jan 2020 16:18:13 -0500
Subject: [PATCH] Run minikube docker-env in a shell-independent way (#18823)

---
 content/en/docs/setup/learning-environment/minikube.md | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/content/en/docs/setup/learning-environment/minikube.md b/content/en/docs/setup/learning-environment/minikube.md
index 3135a6af30..1ca6bb9982 100644
--- a/content/en/docs/setup/learning-environment/minikube.md
+++ b/content/en/docs/setup/learning-environment/minikube.md
@@ -263,11 +263,7 @@ When using a single VM for Kubernetes, it's useful to reuse Minikube's built-in
 Be sure to tag your Docker image with something other than latest and use that tag to pull the image. Because `:latest` is the default value, with a corresponding default image pull policy of `Always`, an image pull error (`ErrImagePull`) eventually results if you do not have the Docker image in the default Docker registry (usually DockerHub).
 {{< /note >}}
 
-To work with the Docker daemon on your Mac/Linux host, use the `docker-env command` in your shell:
-
-```shell
-eval $(minikube docker-env)
-```
+To work with the Docker daemon on your Mac/Linux host, run the last line from `minikube docker-env`.
 
 You can now use Docker at the command line of your host Mac/Linux machine to communicate with the Docker daemon inside the Minikube VM: