Repository navigation
feat(runs): Firecracker runtime for runs - #254
Merged
Merged
Conversation
Runs can execute in a Firecracker microVM with a separate guest kernel to isolate untrusted code. Nodes without Firecracker keep serving Docker runs.
A run that never reaches the expected state now shows where it stopped, so a slow image pull and a stuck worker can be told apart.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs can execute in a Firecracker microVM with a separate guest kernel to isolate untrusted code. Firecracker stays off until a guest kernel is configured. Nodes without it keep serving Docker runs.