Previously, when the Kubernetes setup (Kubernetes 0.5.2) did not work, I was using Ubuntu 14.04, VirtualBox 1.6.5 and Vagrant 4.3.22.
I tried the setup again on a different machine and it worked. This time around I used Mac OS X 10.8.5, VirtualBox 1.6.5 and Vagrant 4.3.20 [1]. Raj, used Ubuntu 14.04, VirtualBox 1.7.2 and Vagrant 4.3.22 to test the setup and it worked. Therefore, could it be that VirtualBox 1.6.5 is not compatible with Vagrant 4.3.22? [1] Admin16s-MacBook-Air:~ Admin16$ cd /Users/Admin16/Documents/Stratos_4.1.0/stratos-kub-test Admin16s-MacBook-Air:stratos-kub-test Admin16$ git clone https://github.com/imesh/kubernetes-vagrant-setup.git fatal: destination path 'kubernetes-vagrant-setup' already exists and is not an empty directory. Admin16s-MacBook-Air:stratos-kub-test Admin16$ cd .. Admin16s-MacBook-Air:Stratos_4.1.0 Admin16$ 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 Admin16s-MacBook-Air:Stratos_4.1.0 Admin16$ cd kubernetes-vagrant-setup/ Admin16s-MacBook-Air:kubernetes-vagrant-setup Admin16$ vagrant up /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: warning: Insecure world writable dir /usr/local in PATH, mode 040777 /Applications/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /usr/local in PATH, mode 040777 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:///Users/Admin16/Documents/Stratos_4.1.0/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_1424686994035_16430 ==> 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:///Users/Admin16/Documents/Stratos_4.1.0/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_1424687019796_54115 ==> 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 Admin16s-MacBook-Air:kubernetes-vagrant-setup Admin16$ vagrant ssh master /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.6.5/lib/vagrant/pre-rubygems.rb:31: warning: Insecure world writable dir /usr/local in PATH, mode 040777 /Applications/Vagrant/embedded/gems/gems/bundler-1.6.6/lib/bundler/runtime.rb:222: warning: Insecure world writable dir /usr/local in PATH, mode 040777 CoreOS (alpha) core@master ~ $ sudo systemctl restart controller-manager core@master ~ $ kubecfg list minions Minion identifier ---------- 172.17.8.100 core@master ~ $ ifconfig docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 10.100.28.1 netmask 255.255.255.0 broadcast 0.0.0.0 ether 56:84:7a:fe:97:99 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fef3:5f1b prefixlen 64 scopeid 0x20<link> ether 08:00:27:f3:5f:1b txqueuelen 1000 (Ethernet) RX packets 148750 bytes 209071910 (199.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 65441 bytes 3658875 (3.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.56.102 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::a00:27ff:fe98:ed0c prefixlen 64 scopeid 0x20<link> ether 08:00:27:98:ed:0c txqueuelen 1000 (Ethernet) RX packets 35 bytes 4846 (4.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 50 bytes 4482 (4.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 flannel0: flags=81<UP,POINTOPOINT,RUNNING> mtu 1472 inet 10.100.28.0 netmask 255.255.0.0 destination 10.100.28.0 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 15 bytes 840 (840.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15 bytes 4560 (4.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 17283 bytes 2470206 (2.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 17283 bytes 2470206 (2.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 core@master ~ $ ping www.google.com PING www.google.com (222.165.163.24) 56(84) bytes of data. 64 bytes from 222.165.163.24: icmp_seq=1 ttl=63 time=29.1 ms 64 bytes from 222.165.163.24: icmp_seq=2 ttl=63 time=13.0 ms 64 bytes from 222.165.163.24: icmp_seq=3 ttl=63 time=4.86 ms 64 bytes from 222.165.163.24: icmp_seq=4 ttl=63 time=4.76 ms 64 bytes from 222.165.163.24: icmp_seq=5 ttl=63 time=4.32 ms 64 bytes from 222.165.163.24: icmp_seq=6 ttl=63 time=9.74 ms 64 bytes from 222.165.163.24: icmp_seq=7 ttl=63 time=24.5 ms 64 bytes from 222.165.163.24: icmp_seq=8 ttl=63 time=7.99 ms 64 bytes from 222.165.163.24: icmp_seq=9 ttl=63 time=80.7 ms ^C --- www.google.com ping statistics --- 10 packets transmitted, 9 received, 10% packet loss, time 9024ms rtt min/avg/max/mdev = 4.324/19.916/80.794/23.107 ms 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 2:41 PM, Mariangela Hills <mariang...@wso2.com> wrote: > 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 >> > >
