Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use containerd runtime by default #11406

Closed
ilya-zuyev opened this issue May 13, 2021 · 2 comments
Closed

Use containerd runtime by default #11406

ilya-zuyev opened this issue May 13, 2021 · 2 comments
Labels
co/runtime/containerd kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@ilya-zuyev
Copy link
Contributor

It looks like in the next years Kubernetes development will be based on containerd as CRI implementation. Let's follow it and switch default container runtime from docker to containerd.
@ilya-zuyev ilya-zuyev added the triage/discuss Items for discussion label May 13, 2021
@afbjorklund
Copy link
Collaborator

afbjorklund commented May 14, 2021 •
edited
Loading

This is duplicating the "MEP" process: #9639

https://github.com/kubernetes/minikube/blob/master/enhancements/proposed/20201230-containerd-default/container-default.md

The problem is not so much changing the default container runtime, the main issue are the implications like docker-env disappearing and BuildKit installation still having some usability issues.

Also it seems like kind and kubeadm have very different strategies on which containerd to choose. Where kind uses latest/greatest from upstream, but kubeadm uses the one from docker ?

#11327 #10089

@afbjorklund afbjorklund added triage/duplicate Indicates an issue is a duplicate of other open issue. co/runtime/docker Issues specific to a docker runtime co/runtime/containerd and removed co/runtime/docker Issues specific to a docker runtime labels May 14, 2021
@spowelljr spowelljr added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels May 17, 2021
@tharun208 tharun208 mentioned this issue May 21, 2021
Closed
@medyagh
Copy link
Member

medyagh commented May 24, 2021

we should decide based on users needs, minikube's main users are local developers. current bechmarks for image build https://minikube.sigs.k8s.io/docs/benchmarks/imagebuild/ shows docker runtime has better image build

@andriyDev andriyDev removed the triage/discuss Items for discussion label Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/runtime/containerd kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@medyagh @afbjorklund @sharifelgamal @andriyDev @spowelljr @ilya-zuyev