Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Add containerd support as the container runtime #209

Closed
luxas opened this issue Jul 17, 2019 · 1 comment · Fixed by #337
Closed

Add containerd support as the container runtime #209

luxas opened this issue Jul 17, 2019 · 1 comment · Fixed by #337
Labels
area/ecosystem Ecosystem-related integrations area/security Issues related to security help wanted Extra attention is needed kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. kind/refactor Categorizes issue or PR as related to refactoring code. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@luxas
Copy link
Contributor

luxas commented Jul 17, 2019

This implementation is harder than for docker:

  • Need to craft the OCI spec manually when running the container
  • Need to write custom code for handling logs
  • Need to write custom code for attaching to the VM

However, there are benefits too:

  • Smaller scope => less resource usage, overhead and attack surface
  • Ignite can be used in "docker-less" environments
  • Choice, we won't "lock in" to docker
  • CNI comes for free, no need for us to use the docker CNI impl we have
@luxas luxas added area/ecosystem Ecosystem-related integrations area/security Issues related to security kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. kind/refactor Categorizes issue or PR as related to refactoring code. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jul 17, 2019
@luxas luxas added this to the v0.5.0 milestone Jul 17, 2019
@luxas
Copy link
Contributor Author

luxas commented Jul 30, 2019

Moving this to v0.6.0, we'll try to get a focused release out for v0.5.0 containing mostly internal changes before attacking this.

With #67 fixed, this should now be completely doable. If someone from the community would like to give it a go, let us know 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/ecosystem Ecosystem-related integrations area/security Issues related to security help wanted Extra attention is needed kind/design Categorizes issue or PR as related to the design of the project. kind/feature Categorizes issue or PR as related to a new feature. kind/refactor Categorizes issue or PR as related to refactoring code. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant