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

Reply via email to