Hi Imesh, I tried the Kubernetes setup but it still does not work for me.
mariangela@mariangela-ThinkPad-T520:~$ git clone https://github.com/imesh/kubernetes-vagrant-setup.git Cloning into 'kubernetes-vagrant-setup'... remote: Counting objects: 60, done. remote: Compressing objects: 100% (47/47), done. remote: Total 60 (delta 34), reused 39 (delta 13) Unpacking objects: 100% (60/60), done. Checking connectivity... done. mariangela@mariangela-ThinkPad-T520:~$ ls Desktop Public Documents stratos Downloads Templates examples.desktop Ubuntu14.4-terminal kubernetes-vagrant-setup vagrant-kubernetes-setup.tgz kube-setup Videos Music virtualbox-4.3_4.3.20-96996~Ubuntu~raring_amd64.deb OS X-10.8.5-terminal VirtualBox VMs Pictures mariangela@mariangela-ThinkPad-T520:~$ ^C mariangela@mariangela-ThinkPad-T520:~$ cd kubernetes-vagrant-setup mariangela@mariangela-ThinkPad-T520:~/kubernetes-vagrant-setup$ vagrant up Bringing machine 'discovery' up with 'virtualbox' provider... Bringing machine 'master' up with 'virtualbox' provider... ==> discovery: Box 'coreos-alpha' could not be found. Attempting to find and install... discovery: Box Provider: virtualbox discovery: Box Version: = 536.0.0 ==> discovery: Loading metadata for box 'coreos_production_vagrant.json' discovery: URL: file:///home/mariangela/kubernetes-vagrant-setup/coreos_production_vagrant.json ==> discovery: Adding box 'coreos-alpha' (v536.0.0) for provider: virtualbox discovery: Downloading: http://alpha.release.core-os.net/amd64-usr/536.0.0/coreos_production_vagrant.box discovery: Calculating and comparing box checksum... ==> discovery: Successfully added box 'coreos-alpha' (v536.0.0) for 'virtualbox'! ==> discovery: Importing base box 'coreos-alpha'... ==> discovery: Matching MAC address for NAT networking... ==> discovery: Checking if box 'coreos-alpha' is up to date... ==> discovery: Setting the name of the VM: kubernetes-vagrant-setup_discovery_1424681465144_19115 ==> discovery: Clearing any previously set network interfaces... ==> discovery: Preparing network interfaces based on configuration... discovery: Adapter 1: nat discovery: Adapter 2: hostonly ==> discovery: Forwarding ports... discovery: 22 => 2222 (adapter 1) ==> discovery: Running 'pre-boot' VM customizations... ==> discovery: Booting VM... ==> discovery: Waiting for machine to boot. This may take a few minutes... discovery: SSH address: 127.0.0.1:2222 discovery: SSH username: core discovery: SSH auth method: private key discovery: Warning: Connection timeout. Retrying... ==> discovery: Machine booted and ready! ==> discovery: Setting hostname... ==> discovery: Configuring and enabling network interfaces... ==> discovery: Running provisioner: file... ==> discovery: Running provisioner: shell... discovery: Running: inline script ==> master: Box 'coreos-alpha' could not be found. Attempting to find and install... master: Box Provider: virtualbox master: Box Version: = 536.0.0 ==> master: Loading metadata for box 'coreos_production_vagrant.json' master: URL: file:///home/mariangela/kubernetes-vagrant-setup/coreos_production_vagrant.json ==> master: Adding box 'coreos-alpha' (v536.0.0) for provider: virtualbox ==> master: Importing base box 'coreos-alpha'... ==> master: Matching MAC address for NAT networking... ==> master: Checking if box 'coreos-alpha' is up to date... ==> master: Setting the name of the VM: kubernetes-vagrant-setup_master_1424681498206_13481 ==> master: Fixed port collision for 22 => 2222. Now on port 2200. ==> master: Clearing any previously set network interfaces... ==> master: Preparing network interfaces based on configuration... master: Adapter 1: nat master: Adapter 2: hostonly ==> master: Forwarding ports... master: 4001 => 4001 (adapter 1) master: 22 => 2200 (adapter 1) ==> master: Running 'pre-boot' VM customizations... ==> master: Booting VM... ==> master: Waiting for machine to boot. This may take a few minutes... master: SSH address: 127.0.0.1:2200 master: SSH username: core master: SSH auth method: private key master: Warning: Connection timeout. Retrying... ==> master: Machine booted and ready! ==> master: Setting hostname... ==> master: Configuring and enabling network interfaces... ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script ==> master: Running provisioner: file... ==> master: Running provisioner: shell... master: Running: inline script mariangela@mariangela-ThinkPad-T520:~/kubernetes-vagrant-setup$ vagrant ssh master CoreOS (alpha) Update Strategy: No Reboots core@master ~ $ sudo systemctl restart controller-manager core@master ~ $ kubecfg list minions Minion identifier ---------- core@master ~ $ kubecfg list minions Minion identifier ---------- core@master ~ $ ping google.com PING google.com (222.165.163.53) 56(84) bytes of data. ^C --- google.com ping statistics --- 9 packets transmitted, 0 received, 100% packet loss, time 7999ms core@master ~ $ kubecfg list minions Minion identifier ---------- core@master ~ $ kubecfg list minions Minion identifier ---------- core@master ~ $ Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com <http://wso2.com/events/> On Mon, Feb 23, 2015 at 8:27 AM, Imesh Gunaratne <im...@apache.org> wrote: > Great! Nice to hear that Raj! I also did a fresh installation using this > repo and its working. > > On Mon, Feb 23, 2015 at 1:53 PM, Rajkumar Rajaratnam <rajkum...@wso2.com> > wrote: > >> Great. Docker commands are working now. Thanks Imesh. >> >> On Mon, Feb 23, 2015 at 1:34 PM, Imesh Gunaratne <im...@apache.org> >> wrote: >> >>> Hi Raj, >>> >>> Yes there was a problem, I just changed the coreos-alpha version to >>> 536.0.0 and it seems to be working now. >>> >>> Can you please take a pull and try again? >>> >>> Thanks >>> >>> On Mon, Feb 23, 2015 at 12:42 PM, Rajkumar Rajaratnam < >>> rajkum...@wso2.com> wrote: >>> >>>> >>>> >>>> On Mon, Feb 23, 2015 at 12:38 PM, Sajith Kariyawasam <saj...@wso2.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Mon, Feb 23, 2015 at 12:27 PM, Rajkumar Rajaratnam < >>>>> rajkum...@wso2.com> wrote: >>>>> >>>>>> Hi Imesh, >>>>>> >>>>>> Docker commands are not working on my setup. Can you please try and >>>>>> let me know whether docker commands are working on your setup? >>>>>> >>>>> >>>>> Commands are not working in your master node or in your host machine? >>>>> >>>> >>>> On master node. >>>> >>>> >>>>> >>>>> What are the messages you get when you execute docker commands? >>>>> >>>> >>>> Commands are just hanging. No messages. >>>> >>>> Getting the following error when tailing journalctl -f on master node. >>>> >>>> Feb 23 07:10:40 master systemd[1]: docker.service: main process exited, >>>> code=exited, status=1/FAILURE >>>> Feb 23 07:10:40 master systemd[1]: Unit docker.service entered failed >>>> state. >>>> Feb 23 07:10:40 master systemd[1]: docker.service failed. >>>> >>>> >>>>> Im guessing docker is not properly started. >>>>> >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Mon, Feb 23, 2015 at 12:24 PM, Imesh Gunaratne <im...@apache.org> >>>>>> wrote: >>>>>> >>>>>>> Hi Devs, >>>>>>> >>>>>>> I have now fixed the issue we encountered in latest coreos-alpha >>>>>>> release and created a new Vagrant setup: >>>>>>> >>>>>>> git clone https://github.com/imesh/kubernetes-vagrant-setup.git >>>>>>> cd kubernetes-vagrant-setup >>>>>>> vagrant up >>>>>>> vagrant ssh master >>>>>>> core@master ~ $sudo systemctl restart controller-manager >>>>>>> [wait for around 30 sec] >>>>>>> core@master ~ $ kubecfg list minions >>>>>>> Minion identifier >>>>>>> ---------- >>>>>>> 172.17.8.100 >>>>>>> >>>>>>> Please try this out and let me know if there are any issues. >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> -- >>>>>>> Imesh Gunaratne >>>>>>> >>>>>>> Technical Lead, WSO2 >>>>>>> Committer & PMC Member, Apache Stratos >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rajkumar Rajaratnam >>>>>> Committer & PMC Member, Apache Stratos >>>>>> Software Engineer, WSO2 >>>>>> >>>>>> Mobile : +94777568639 >>>>>> Blog : rajkumarr.com >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Rajkumar Rajaratnam >>>> Committer & PMC Member, Apache Stratos >>>> Software Engineer, WSO2 >>>> >>>> Mobile : +94777568639 >>>> Blog : rajkumarr.com >>>> >>> >>> >>> >>> -- >>> Imesh Gunaratne >>> >>> Technical Lead, WSO2 >>> Committer & PMC Member, Apache Stratos >>> >> >> >> >> -- >> Rajkumar Rajaratnam >> Committer & PMC Member, Apache Stratos >> Software Engineer, WSO2 >> >> Mobile : +94777568639 >> Blog : rajkumarr.com >> > > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos >
