On 1/29/19 12:41 PM, mabi wrote:
> Thanks for your answer.
>
> Now this would be for a production server for okd.io 3.11 that's why I
> chose CentOS Atomic Host. As far as I know Fedora is not for
> production server usage right?
>
> So my question is: what do people use for production okd.io with cri-o
> as container runtime?
>
Standard OS's Fedora/CentOS/RHEL.
>
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, January 29, 2019 1:20 PM, Daniel Walsh <dwa...@redhat.com>
> wrote:
>
>> I would figure you need it on Fedora CoreOS. We did some
>> experimenting with CRI-O in a system container but decided this
>> caused too many issues.
>>
>>
>> On 1/29/19 11:50 AM, Scott McCarty wrote:
>>> Chris/Derrick,
>>> Have either of you ran into this?
>>>
>>> Best Regards
>>> Scott M
>>>
>>> On Fri, Jan 25, 2019 at 12:56 PM mabi <m...@protonmail.ch
>>> <mailto:m...@protonmail.ch>> wrote:
>>>
>>> Hello,
>>>
>>> I would like to use CRI-O (https://cri-o.io/) on CentOS Atomic
>>> Host along with or instead of Docker but it looks like there are
>>> no cri-o packages for Atomic Host:
>>>
>>> # rpm-ostree install cri-o
>>> Checking out tree 4b20905... done
>>> Enabled rpm-md repositories: base updates extras
>>> rpm-md repo 'base' (cached); generated: 2018-11-25 16:00:34
>>> rpm-md repo 'updates' (cached); generated: 2019-01-24 13:56:44
>>> rpm-md repo 'extras' (cached); generated: 2018-12-10 16:00:03
>>> Importing metadata [=============] 100%
>>> error: No package matches 'cri-o'
>>>
>>> Is there any other ways I can get CRI-O running on Atomic Host?
>>> and/or is it planned to be also available on Atomic Hosting in
>>> the near future?
>>>
>>> Regards,
>>> Mabi
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>> -- Scott McCarty, RHCA Product Management - Containers, Red Hat
>>> Enterprise Linux & OpenShift Email: smcca...@redhat.com
>>> <mailto:smcca...@redhat.com> Phone: 312-660-3535 Cell: 330-807-1043
>>> Web: http://crunchtools.com Learning Container Engines by Demo:
>>> https://goo.gl/zMrLqR
>>
>>
>
