support cri-o as a container-runtime

[vbatts]

https://github.com/kubernetes-incubator/cri-o is runs under openshift 3.6 and newer, quite nicely.

This is now an open PR with minikube, and would be great to have this in minishift as well.
kubernetes/minikube#1998

[LalatenduMohanty]

@vbatts Thanks. We will take a look and get back to you.

[vbatts]

👍

[gbraad]

I noticed you proposed cri-o as a runtime for minikube. We are in the process of supporting this image, too. See #1058

[gbraad]

@vbatts are packages ready for CentOS to support this?

[praveenkumar]

http://cbs.centos.org/koji/packageinfo?packageID=5695 looks like cri-o package is build on cbs also but not sure how mature this is and how to consume when we build our own ISO. Might be we will keep this as experiment feature for minishift till it part of offical repos?

[gbraad]

adding runtime selections from minishift as experimental feature is not difficult, but experimental features for the ISO is slightly more difficult to handle. We will have to think how to handle this.

[gbraad]

One of the things we haven't handled yet is the version number problem related to the ISO we use. For minikube it is easier to handle, as this is part of the release. In our case I want to do feature detection for the ISO we use... and based on that allow certain features to happen... like mounting CIFS, etc.

However, a runtime selection happens during the provisioning, so the request might only fail after the VM started, and the provisioning just started...

How do you see this, @praveenkumar ?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gbraad]

Still of interest to us, although we can also use the Minikube ISO now.

[gbraad]

@vbatts I know for Fedora this is easy to do... but what needs to be provided on CentOS to make this work?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[vbatts]

bump

@gbraad I missed your question. My apologies. I thought there were centos7 packages! :-\ perhaps since there are RHEL builds of it then it can't be in EPEL now? I'm confused. @lsm5 do you know where/how to get cri-o packages to centos7?

[gbraad]

We have since made a Fedora ISO: https://github.com/minishift/minishift-fedora-iso
In this ISO we can easily add crio, podman, etc: minishift/minishift-fedora-iso#14

[lsm5]

On Wed, Nov 07, 2018 at 04:54:50AM -0800, Vincent Batts wrote: bump @gbraad I missed your question. My apologies. I thought there were centos7 packages! :-\ perhaps since there are RHEL builds of it then it can't be in EPEL now? I'm confused. @lsm5 do you know where/how to get cri-o packages to centos7?

@fkluknav can you please provide info on ^

…

-- Lokesh IRC, GitHub: lsm5 GPG: 0xC7C3A0DD https://keybase.io/lsm5

[gbraad]

we do have a PR for the Fedora ISO: minishift/minishift-fedora-iso#14

[lsm5]

On Wed, Nov 07, 2018 at 05:54:07AM -0800, Gerard Braad wrote: We have since made a Fedora ISO: https://github.com/minishift/minishift-fedora-iso In this ISO we can easily add crio, podman, etc: minishift/minishift-fedora-iso#14

RE: fedora, cri-o is now being supported as a module and not as a vanilla rpm. See the 1.11, 1.12 branches in https://src.fedoraproject.org/rpms/cri-o

…

-- Lokesh IRC, GitHub: lsm5 GPG: 0xC7C3A0DD https://keybase.io/lsm5

[gbraad]

RE: fedora, cri-o is now being supported as a module and not as a vanilla rpm.

@praveenkumar ^^

[fkluknav]

Centos 7 contains cri-o-3.10, available at http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin310/
Repo file for yum with a link pointing there is in centos-release-openshift-origin310.rpm, available from centos extras.
Cri-o-3.11 should be available soon, together with openshift 3.11. In the meantime, it is in https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/
Podman should be similarly available soon. In the meantime, https://buildlogs.centos.org/centos/7/virt/x86_64/container/
@gbraad, does it andswer your question?

[fkluknav]

@praveenkumar, about maturity, it should be a rebuild of what Red Hat ships, for good or ill.

[praveenkumar]

@vbatts We do have a PR for centos side about same but as part of minishift we uses oc cluster up which doesn't support a different container runtime than docker. Moving forward with OpenShift 4.0 side oc cluster up no longer exist, which means we need a different way to bring up a single node cluster. I am not sure what benefit a minishift user get just including it as a package and not able to consume it due to cluster up limitation.

• [WIP] Issue #242 Add cri-o, buildah and podman packages minishift-centos-iso#243

[gbraad]

It would be useful for the fact that people can use `minishift start --no-provision` to stand up a cri-o, podman host... but this is not beneficial to use at the moment. I would suggest that we can refer to the PR and the artifacts if they wanna test/play with this.

[thomasmckay]

Is this a "thing" in minishift? Are there instructions somewhere?

[gbraad]

It is not supported, as OpenShift `oc cluster up` does not support being bootstrapped without `docker`. there are some blogposts from praveen... will look them up for you.

…

On Sat, Jan 26, 2019 at 5:49 AM thomasmckay ***@***.***> wrote: Is this a "thing" in minishift? Are there instructions somewhere? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

-- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ]