I'm installing a Kubernetes cluster on a virtual Ubuntu environment, already installed over Docker and Boot2Docker (Windows7/Intel64) components.

I've successfully installed the following software components:

. Boot2Docker . Docker 1.7.1 . Ubuntu on Docker 14.04 . Latest Kubernetes from GitHub 1.3

and followed the install instructions at: http://kubernetes.io/docs/getting-started-guides/ubuntu/

My questions:

. Why do I get the error message at kube-up.sh cluster startup:
ssh: connect to host 10.10.103.250 port 22: Connection timed out;

. How can I produce a log file that shows eventual error messages during the kubernetes cluster startup process;

. Why does the command: kubectl get nodes not conect ssh to localhost. Is it active?

Below the details of the installation flow:

root@a7d243d9a7c5:/# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.4 LTS
Release:        14.04
Codename:       trusty

# To activate the container:  
docker start a7d243d9a7c5
docker attach a7d243d9a7c5

# To generate ssh certificates
root@a7d243d9a7c5:~# mkdir ~/.shh
root@a7d243d9a7c5:~# chmod 700 ~/.shh
root@a7d243d9a7c5:~# ssh-keygen -t rsa

root@a7d243d9a7c5:/kubernetes# export PATH="/kubernetes/cluster/ubuntu/binaries:$PATH"
root@a7d243d9a7c5:/kubernetes# echo $PATH
/kubernetes/cluster/ubuntu/binaries:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

root@a7d243d9a7c5:/# export KUBE_VERSION=1.1.8
root@a7d243d9a7c5:/# export FLANNEL_VERSION=0.5.5
root@a7d243d9a7c5:/# export ETCD_VERSION=2.2.0
root@a7d243d9a7c5:/# export KUBERNETES_PROVIDER=ubuntu

cd  kubernetes
./cluster/kube-up.sh
Done! All your binaries locate in kubernetes/cluster/ubuntu/binaries directory
Deploying master and node on machine 10.10.103.250

ssh: connect to host 10.10.103.250 port 22: Connection timed out

kubectl get nodes 
The connection to the server localhost:8080 was refused - did you specify the right host or port?

The present error is very similar to this report: Running kubernetes on ubuntu

Update: Why to use Boot2docker There are a number of reasons for such construction and the scenarios is not only limited to Windows, but also applies to other base operating systems. First, not to loose the warranted OEM installation of the original manufacturer, that beside commercial web workload also handles energy and device management. Second, the purpose of the Docker environment is primarily to create an isolated development space to execute new package builds with specialized prerequisites, eventually also to run a basic run-time test. At the end of the process the images are uploaded into a cloud environment, having stable behaviour. Yet another point to comment is that a minimal Ubuntu under such environment already demonstrated excellent performance.