From 6d2aa28ccd93843a8a6362f9a1407f3c895d8b0e Mon Sep 17 00:00:00 2001 From: Qiming Teng Date: Thu, 4 Jan 2018 13:01:48 +0800 Subject: [PATCH] Fix proxy environment variables when using minikube Closes: #5170 --- docs/getting-started-guides/minikube.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md index 57fbf6cadb..fe8ca8aadd 100644 --- a/docs/getting-started-guides/minikube.md +++ b/docs/getting-started-guides/minikube.md @@ -160,7 +160,7 @@ This command also configures your [kubectl](/docs/user-guide/kubectl-overview/) If you are behind a web proxy, you will need to pass this information in e.g. via ``` -https_proxy= minikube start --docker-env HTTP_PROXY= --docker-env HTTPS_PROXY= --docker-env NO_PROXY=192.168.99.0/24 +https_proxy= minikube start --docker-env http_proxy= --docker-env https_proxy= --docker-env no_proxy=192.168.99.0/24 ``` Unfortunately just setting the environment variables will not work. @@ -325,8 +325,8 @@ To do this, pass the required environment variables as flags during `minikube st For example: ```shell -$ minikube start --docker-env HTTP_PROXY=http://$YOURPROXY:PORT \ - --docker-env HTTPS_PROXY=https://$YOURPROXY:PORT +$ minikube start --docker-env http_proxy=http://$YOURPROXY:PORT \ + --docker-env https_proxy=https://$YOURPROXY:PORT ``` If your Virtual Machine address is 192.168.99.100, then chances are your proxy settings will prevent kubectl from directly reaching it.