I had issues on my work Mac, but the principles are similar. The documentation is easy enough to follow to get MiniKube to point to the corporate proxy, but it expects you to be an authenticated user. In my case, I run tinyproxy on my local machine which listens on port 8888 and then sends anything destined for the outside world via cntlm on port 3128. For this to work, MiniKube has to talk to my mac (its host) which is achieved with the 10.0.2.2 address like so: --docker-env HTTP_PROXY=http://10.0.2.2:8888 --docker-env HTTPS_PROXY=http://10.0.2.2:8888 I also had issues with "x509: certificate signed by unknown authority" on the docker pull commands within minikube, which I solved with the --insecure-registry argument. My entire minikube startup command looks like this, which [finally] works for me:

minikube start --docker-env HTTP_PROXY=http://10.0.2.2:8888 --docker-env HTTPS_PROXY=http://10.0.2.2:8888 --docker-env NO_PROXY=10.0.2.2,192.168.99.100 --insecure-registry="k8s.gcr.io"

set NO_PROXY="$NO_PROXY,192.168.211.158/8443"

That slash is not the port, it's the CIDR which defines how many IPs should be excluded from the proxy. Separately, it appears you somehow included the colon in the one provided to --docker-env, which I think is also wrong.

And, the $NO_PROXY, syntax in your set command is also incorrect, since that's the unix-y way of referencing environment variables -- you would want set NO_PROXY="%NO_PROXY%,... just be careful since unless you already have a variable named NO_PROXY, that set will expand to read set NO_PROXY=",192.168.etcetc" which I'm not sure is legal syntax for that variable.