Thanks for reply. I've tried to assign 8-12gb of memory and 4-6 processors.
Still the same issue. I've also tried to completely reinstall docker.

On Wed, Oct 25, 2017 at 5:28 PM, Cesar Wong <[email protected]> wrote:

> I just tried it on my mac and things ran ok for me. I would check the
> memory/cpu you're assigning Docker. I'd at least give it 4-6gb of memory
> and half to all your processors.
> On Wed, Oct 25, 2017 at 11:22 AM, Jan Hellar <[email protected]> wrote:
>
> Hi Cesar,
>
> I've just used "oc cluster up" with no other parameters.
>
> Regards,
> Jan
>
> On Wed, Oct 25, 2017 at 4:56 PM, Cesar Wong <[email protected]> wrote:
>
>> Hi Jan,
>>
>> Can you include the exact command you're using to start cluster up ? Are
>> you specifying a different version of the images?
>>
>> On Wed, Oct 25, 2017 at 8:16 AM, Jan Hellar <[email protected]> wrote:
>>
>> Hi,
>>
>> recently I have tried to run `oc cluster up` on mac. When running `oc
>> cluster status` I get `Notice: Router is not yet ready`. When running
>> `oc get pods` in `default` project, I can see that pod for router is in
>> ContainerCreating state. Looking at events for the router pod I can see
>> these two events:
>> - Sandbox changed - Pod sandbox changed, it will be killed and
>> re-created. 12 times in the last minute
>> - Failed sync - Error syncing pod - 13 times in the last minute
>>
>> I have latest version of docker installed (Version 17.09.0-ce-mac35
>> (19611)). Tried latest version (3.6.0) of openshift-cli from both github
>> and brew.
>>
>> Can anybody help with this issue? Thank you.
>>
>> Best regards,
>>
>> Jan Hellar
>>
>>
>
>
> --
> Jan Hellar
>
>


-- 
Jan Hellar
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to