Internet via proxy about dcos-kubernetes-quickstart HOT 8 CLOSED

Hi @ezreal92170, this sounds like a routing or firewall issue. The proxy should not matter, as long as the kubelet container has a route to the Internet. If you enter the container, can you ping the GCR IP?

nsenter -t <KUBELET PID> -m -n -p -w

from dcos-kubernetes-quickstart.

Just to clarify, in my environment i don't have direct access to Internet. I can only use http and https protocol to access the internet and only through a "corporate" proxy.

In this error message

Error response from daemon: {"message":"Get https://gcr.io/v1/_ping: dial tcp 74.125.133.82:443: i/o timeout"}

we see that the daemon try direct connect to the Internet (ignoring my docker core os host configuration) because dns resolution happened. The direct connection will always fail in my environnement, i must to try to configure a http proxy for the daemon

from dcos-kubernetes-quickstart.

Thanks for the details. We are currently in the process of "air gapping" the framework. It will be runnable behind the firewall soon.

from dcos-kubernetes-quickstart.

Thanks, if you have some clue to modify inside container any configuration before a new released i can do some test.

from dcos-kubernetes-quickstart.

This will be fixed with a new release to happen next week.

from dcos-kubernetes-quickstart.

thx i will be happy to test that.

from dcos-kubernetes-quickstart.

Can you try the new release and report back?

from dcos-kubernetes-quickstart.

Closing. Please report back if you encounter any issues.

from dcos-kubernetes-quickstart.