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

[QUESTION] could i use ignite as CRI runtime for kubelet? #162

Closed
Slach opened this issue Jul 14, 2019 · 2 comments
Closed

[QUESTION] could i use ignite as CRI runtime for kubelet? #162

Slach opened this issue Jul 14, 2019 · 2 comments
Labels
documentation/confusing Address confusing documentation text documentation/content-gap Address a content gap in the documentation priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.4.2

Comments

@Slach
Copy link

Slach commented Jul 14, 2019

could somebody add to documentation howto use ignite as CRI in Kubernetes? for running firecracker VM instead of containers with namespaces?
@luxas
Copy link
Contributor

luxas commented Jul 15, 2019 •
edited
Loading

Hi @Slach 👋! Good question
Let's add this question to the coming FAQ.md (#147).

In short, no, you can't use Ignite as a CRI runtime, as it doesn't run containers.
Ignite runs real VMs, based on a OCI image's rootfs.

If you want to run containers with Firecracker isolation, check out https://github.com/firecracker-microvm/firecracker-containerd.

Also some more info on this thread: https://twitter.com/jschnatterer/status/1150042240888332288

I'll keep this open until we have this in the FAQ.

@luxas luxas added documentation/content-gap Address a content gap in the documentation documentation/confusing Address confusing documentation text priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jul 15, 2019
@luxas luxas added this to the v0.4.2 milestone Jul 15, 2019
@luxas luxas added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Jul 15, 2019
@luxas luxas mentioned this issue Jul 16, 2019
Merged
@luxas
Copy link
Contributor

luxas commented Jul 16, 2019

This is now fixed with #197

@luxas luxas closed this as completed Jul 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
documentation/confusing Address confusing documentation text documentation/content-gap Address a content gap in the documentation priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.4.2
Development

No branches or pull requests
2 participants
@Slach @luxas