Using `kid` behind HTTP proxy?
I'm trying to use kid to set up Kubernetes on my workstation, which sits behind the usual corporate HTTP proxy. At hte moment kid is blocking here:
$ kid up
WARNING: No swap limit support
Waiting for Kubernetes cluster to become available...
[..]
The Kubernetes setup process seems to be waiting on curl:
$ pstree -a
systemd splash
.
.
|-docker daemon
| |-docker-containe -l /var/run/docker/libcontainerd/docker-containerd.sock --runtime docker-runc
| | |-docker-containe cf4e8b89c4f58f14c5df033eab3aff20a4a0ae8f10e5fc563c74b7137d934853...
| | | |-setup-files.sh /setup-files.sh...
| | | | `-make-ca-cert.sh /make-ca-cert.sh 136.156.124.222...
| | | | `-curl -L -O https://storage.googleapis.com/kubernetes-release/easy-rsa/easy-rsa.tar.gz
That curl process was started by the gcr.io/google_containers/hyperkube-amd64:v1.2.4 image (see attached output of docker inspect. It will not succeed, because it is trying to access https://storage.googleapis.com/kubernetes-release/easy-rsa/easy-rsa.tar.gz directly, without using the HTTP/HTTPS proxy.
Is there a way to tell hyperkube to use an HTTP proxy? Or to set the usual http_proxy, https_proxy and no_proxy environment variables within the containers?
docker-inspect-cf4e8b89c4f58f14c5df033eab3aff20a4a0ae8f10e5fc563c74b7137d934853.txt
Are you using Docker via Docker Machine/boot2docker? If so you could try configuring VirtualBox to use the proxy.