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

Support multiple container runtimes #314

Closed
luxas opened this issue Aug 12, 2019 · 1 comment
Closed

Support multiple container runtimes #314

luxas opened this issue Aug 12, 2019 · 1 comment
Labels
area/UX Let's make Ignite's UX great! kind/enhancement Categorizes issue or PR as related to improving an existing 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 Aug 12, 2019

This requires e.g. having some kind of switch in either ComponentConfig or a flag on ignite and ignite-spawn, and a way to pass related parameters (e.g. the socket the container runtime is listening on)

This is needed for containerd support (#209). We're doing a similar thing for networking now: #310

@luxas luxas added area/UX Let's make Ignite's UX great! 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 Aug 12, 2019
@luxas luxas added this to the v0.6.0 milestone Aug 12, 2019
@luxas luxas added the kind/enhancement Categorizes issue or PR as related to improving an existing feature. label Aug 12, 2019
@luxas
Copy link
Contributor Author

luxas commented Aug 30, 2019

This was fixed in #366

@luxas luxas closed this as completed Aug 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/UX Let's make Ignite's UX great! kind/enhancement Categorizes issue or PR as related to improving an existing 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

No branches or pull requests

1 participant