-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propagate HTTP proxy config into VM #3242
Comments
What about to create a parameter on minikube start --minikube-env http_proxy=url.to.http.proxy:http_port \
--minikube-env https_proxy=url.to.http.proxy:http_port \
--minikube-env no_proxy=localhost,127.0.0.1 Will create the file export http_proxy=url.to.http.proxy:http_port
export https_proxy=url.to.http.proxy:http_port
export no_proxy=localhost,127.0.0.1 In order to use docker environment, sudo -E /usr/bin/kubeadm alpha phase addon kube-dns All the CLI using sudo should use -E switch. Please comment. |
This issue is really annoying, will be awesome to see the fix go through :). Is there a workaround to this? |
@llsousa - That sounds reasonable. As a further iteration, it would be nice if we supported detecting the proxy from the environment, and automatically configured minikube appropriately. "minikube start" should just work in every environment possible. If failing that, it should inform the user on the appropriate action necessary to fix the issue. |
See this is the same issue? this is on win10, with virtualbox Ubuntu OS. C:\Windows\system32>minikube start
Anyone can offer me a temp solution? Thanks much! |
@AdamKong - Your issue seems different, as the error is from outside of the VM environment. I'm pretty sure you just need to tell minikube about your proxy: https://github.com/kubernetes/minikube/blob/master/docs/http_proxy.md |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
I haven't heard any more user complaints on this, so I think we've done a good enough job on this. Closing until someone opens something more specific. |
BUG REPORT
Minikube version (use
minikube version
): v0.30.0cat ~/.minikube/machines/minikube/config.json | grep DriverName
): Virtualboxcat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): v0.30.0What happened:
minikube start --kubernetes-version v1.10.8 --docker-env HTTP_PROXY=xxx --docker-env HTTPS_PROXY=xxx --docker-env NO_PROXY=xxx
is failing in timeout during kubeadm command executionWhat you expected to happen:
minikube starts normally
Anything else do we need to know:
The faulty command is
kubeadm alpha phase addon kube-dns
. I replayed it inside the minikube VM to have more logs :kubeadm is trying to download a file (that actually contains the exact version of kubernetes) but since HTTP proxy settings are not set in VM (they are only set for docker engine through
--docker-env
parameters), this is failing. I found that if you add--kubernetes-version
, no download is done and the command succeeds:So a fix could be to propagate the
--kubernetes-version
passed tominikube start
tokubeadm alpha phase addon kube-dns
command.The text was updated successfully, but these errors were encountered: