Skip to content
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

docker-env http_proxy: Get 192.168.39.49:8443/api/v1/nodes/minikube: Service Unavailable #2706

Closed
julienfr112 opened this issue Apr 11, 2018 · 8 comments
Labels
cause/firewall-or-proxy When firewalls or proxies seem to be interfering co/kvm2-driver KVM2 driver related issues failed/local-networking startup failures due to networking issues kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux

Comments

@julienfr112
Copy link

minikube start --vm-driver="kvm2" --docker-env="http_proxy=$http_proxy" --docker-env="https_proxy=$https_proxy" start

Error starting cluster: timed out waiting to unmark master: getting node minikube: Get https://192.168.39.49:8443/api/v1/nodes/minikube: Service Unavailable

minikube version: v0.26.0
OS
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
"DriverName": "kvm2",
"Boot2DockerURL": "file:///home/julien/.minikube/cache/iso/minikube-v0.26.0.iso",
"ISO": "/home/julien/.minikube/machines/minikube/boot2docker.iso",

@gdamberg
Copy link

gdamberg commented Apr 11, 2018

Same result for me, using virtualbox on Ubuntu 16.04

minikube start --docker-env "HTTPS_PROXY=http://proxy:808" --docker-env 
"HTTP_PROXY=http://proxy:808"  --docker-env "NO_PROXY=localhost,127.0.0.1,192.168.0.0/16"

Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
150.53 MB / 150.53 MB [============================================] 100.00% 0s
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.10.0
Downloading kubelet v1.10.0
Finished Downloading kubelet v1.10.0
Finished Downloading kubeadm v1.10.0
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
E0411 11:52:58.268126    4720 start.go:276] Error starting cluster:  timed out waiting to unmark master: getting node minikube: Get https://192.168.99.100:8443/api/v1/nodes/minikube: Service Unavailable
================================================================================

workaround:

export NO_PROXY="$NO_PROXY,192.168.0.0/16";minikube start --docker-env "HTTPS_PROXY=http://proxy:808" --docker-env 
"HTTP_PROXY=http://proxy:808"  --docker-env "NO_PROXY=localhost,127.0.0.1,192.168.0.0/16"

@alobaidizt
Copy link

Thanks @gdamberg!! Your solution has solved my problem. Can you please explain your solution?

@gdamberg
Copy link

@alobaidizt export NO_PROXY="$NO_PROXY,192.168.0.0/16"- make sure that I have set the no_proxy env variable in the current shell.

minikube start --docker-env "HTTPS_PROXY=http://proxy:808" --docker-env "HTTP_PROXY=http://proxy:808" --docker-env "NO_PROXY=localhost,127.0.0.1,192.168.0.0/16" - start minikube and pass the same no_proxy setting to docker

Specifying 192.168.0.0/16 as the range of ipaddresses that shouldnt go through the Proxy as this is the range (I think) that minikube generate its ip in (and i'm certain that I dont have anything else in that range)

@alobaidizt
Copy link

Thanks @gdamberg!

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 10, 2018
@tstromberg tstromberg added the kind/documentation Categorizes issue or PR as related to documentation. label Sep 19, 2018
@tstromberg tstromberg changed the title BUG minikube does not start with kvm2 driver and enterprise proxy on ubuntu 16.04 docker-env http_proxy: Get 192.168.39.49:8443/api/v1/nodes/minikube: Service Unavailable Sep 19, 2018
@tstromberg tstromberg added cause/firewall-or-proxy When firewalls or proxies seem to be interfering failed/local-networking startup failures due to networking issues os/linux co/kvm2-driver KVM2 driver related issues labels Sep 19, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 20, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/firewall-or-proxy When firewalls or proxies seem to be interfering co/kvm2-driver KVM2 driver related issues failed/local-networking startup failures due to networking issues kind/documentation Categorizes issue or PR as related to documentation. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. os/linux
Projects
None yet
Development

No branches or pull requests

6 participants