Containers-roadmap: [EKS] [request]: CRI-O support

[brianmori]

Tell us about your request
What do you want us to build?

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

CentOS and RHEL 8 have replaced Docker with Buildah and Podman mostly for better security reasons.

Here is a link: https://developers.redhat.com/blog/2019/02/21/podman-and-buildah-for-docker-users/

We would like to have the possibility to use Podman instead of Docker in EKS to not have the Docker daemon running as root for unnecessary reasons.

Are you currently working around this issue?
No, we use Docker at this moment

Additional context
None

Attachments
None

[whereisaaron]

Hi @brianbordini, I think you are mixing up container image build tools with container runtimes. podman and buildah are not alternative runtimes for Kubernetes, but you can choose to use them for building container images and to run them (in the absence of Kubernetes).

Kubernetes switched from the docker runtime to containerd in 2017, and containerd went GA with Kubernetes 1.10 and containerd 1.1 in 2018. So running docker as the container runtime (and thus dockerd) has been optional since then. Inertia and better tooling means running dockerd is still common for Kubernetes installs. As even if you have have switched your clusters to containerd, you can still optionally run the dockerd daemon.

So if you don't want to run dockerd on EKS, you could instead be asking for a switch/option of the containerd runtime (https://github.com/aws/containers-roadmap/issues/313).

https://kubernetes.io/blog/2017/11/containerd-container-runtime-options-kubernetes/
https://kubernetes.io/blog/2018/05/24/kubernetes-containerd-integration-goes-ga/

https://developers.redhat.com/blog/2019/01/29/podman-kubernetes-yaml/
https://developer.ibm.com/articles/templating-and-podman-openshift/

[inductor]

Podman must support CRI first. It’s not a problem with EKS at least for now.

One more thing to note, you can also ask them to support CRI-O which is another Kubernetes compatible runtime mainly developed by RedHat. In fact, it runs as the default container runtime for OpenShift4 so if you want something thinner than Docker, maybe that’s the option.

[haircommander]

One more thing to note, you can also ask them to support CRI-O which is another Kubernetes compatible runtime mainly developed by RedHat...

Hey all, CRI-O and podman maintainer here. I agree with @inductor, what it seems you're looking for @brianbordini is for EKS to support CRI-O. podman is meant as a docker cli replacement, whereas CRI-O is for the kubernetes use-case.

I would love to see CRI-O supported in EKS, and am happy to assist in this endeavour

[brianmori]

Hello,
you are totally correct, I did not deep dive in the matter.
Feel free to close the issue as it is a duplicated for https://github.com/aws/containers-roadmap/issues/313

[haircommander]

Feel free to close the issue as it is a duplicated for #313

I disagree with you here, I'd rename this to [EKS][request] CRI-O support. CRI-O and containerd CRI are two different projects

[jrhoward]

I would love to see support for CRI-O

[nagarajui7]

I would appreciate if EKS starts supporting different run-times like containerd, cri-o

[robrotheram]

As now Kubernetes have announced their deprecation of docker (https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.md#deprecation) I just wondering what EKS roadmap on which container runtime that will be used