I have gotten pretty far by changing different settings on
config-default.sh (definetly not listed in the documentation). Now I am
stuck on only one error. Here is the trace. so the error seems to be this
line *Error: 100: Key not found (/coreos.com <http://coreos.com>) [1] *I
am not even sure where this is coming from and how to fix it?
KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
... Starting cluster using provider: ubuntu
... calling verify-prereqs
... calling kube-up
~/kubernetes/cluster/ubuntu ~/kubernetes/cluster
Prepare flannel 0.5.0 release ...
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 608 0 608 0 0 102 0 --:--:-- 0:00:05 --:--:--
138
100 2757k 100 2757k 0 0 194k 0 0:00:14 0:00:14 --:--:--
739k
Prepare etcd 2.2.0 release ...
% Total % Received % Xferd Average Speed Time Time Time
Current
Dload Upload Total Spent Left
Speed
100 606 0 606 0 0 101 0 --:--:-- 0:00:05 --:--:--
175
100 7183k 100 7183k 0 0 468k 0 0:00:15 0:00:15 --:--:--
1871k
Prepare kubernetes 1.2.4 release ...
Done! All your binaries locate in kubernetes/cluster/ubuntu/binaries
directory
~/kubernetes/cluster
Deploying master and node on machine 192.168.245.244
make-ca-cert.sh
100% 4028 3.9KB/s 00:00
easy-rsa.tar.gz
100% 42KB 42.4KB/s 00:00
config-default.sh
100% 5419 5.3KB/s 00:00
util.sh
100% 29KB 28.6KB/s 00:00
kubelet.conf
100% 644 0.6KB/s 00:00
kube-proxy.conf
100% 684 0.7KB/s 00:00
kubelet
100% 2158 2.1KB/s 00:00
kube-proxy
100% 2233 2.2KB/s 00:00
kube-scheduler.conf
100% 674 0.7KB/s 00:00
etcd.conf
100% 709 0.7KB/s 00:00
kube-controller-manager.conf
100% 744 0.7KB/s 00:00
kube-apiserver.conf
100% 674 0.7KB/s 00:00
kube-apiserver
100% 2358 2.3KB/s 00:00
kube-scheduler
100% 2360 2.3KB/s 00:00
kube-controller-manager
100% 2672 2.6KB/s 00:00
etcd
100% 2073 2.0KB/s 00:00
reconfDocker.sh
100% 2094 2.0KB/s 00:00
kube-apiserver
100% 58MB 58.2MB/s 00:00
kube-scheduler
100% 42MB 42.0MB/s 00:00
kube-controller-manager
100% 52MB 51.8MB/s 00:00
etcdctl
100% 12MB 12.3MB/s 00:00
etcd
100% 14MB 13.8MB/s 00:00
flanneld
100% 11MB 10.8MB/s 00:00
kubelet
100% 60MB 60.3MB/s 00:01
kube-proxy
100% 35MB 34.8MB/s 00:00
flanneld
100% 11MB 10.8MB/s 00:00
flanneld.conf
100% 577 0.6KB/s 00:00
flanneld
100% 2121 2.1KB/s 00:00
flanneld.conf
100% 568 0.6KB/s 00:00
flanneld
100% 2131 2.1KB/s 00:00
[sudo] password to start master:
etcd start/running, process 100639
*Error: 100: Key not found (/coreos.com <http://coreos.com>) [1]*
{"Network":"172.16.0.0/16", "Backend": {"Type": "vxlan"}}
{"Network":"172.16.0.0/16", "Backend": {"Type": "vxlan"}}
docker stop/waiting
docker start/running, process 101035
Connection to 192.168.245.244 closed.
Validating master
Validating [email protected]
Using master 192.168.245.244
cluster "ubuntu" set.
user "ubuntu" set.
context "ubuntu" set.
switched to context "ubuntu".
Wrote config for ubuntu to /home/kant/.kube/config
... calling validate-cluster
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
Waiting for 1 ready nodes. 0 ready nodes, 0 registered. Retrying.
On Fri, Jun 10, 2016 at 8:50 AM, Rodrigo Campos <[email protected]> wrote:
> On Thu, Jun 09, 2016 at 05:16:51PM -0700, kant kodali wrote:
> > I want to start a kubernetes cluster by running kube-up.sh script on my
> > ubuntu machine with no VM. I dont want to go the docker way although
> docker
> > is installed in my computer.
>
> Then, I'd suggest checking the docker image, maybe it's dockerfile too,
> and try
> to do the same on your computer.
>
> But never done that myself, so I really don't know what else to tell you,
> other
> that suggest you to investigate that.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Containers at Google" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-containers/JJEd8vGEpxg/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/google-containers.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Containers at Google" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-containers.
For more options, visit https://groups.google.com/d/optout.
