feat(firecracker): launch with control socket instead of config file#809
Open
Anamika1608 wants to merge 1 commit into
Open
feat(firecracker): launch with control socket instead of config file#809Anamika1608 wants to merge 1 commit into
Anamika1608 wants to merge 1 commit into
Conversation
✅ Deploy Preview for urunc canceled.
|
Firecracker currently boots via --no-api --config-file, which disables its control socket entirely. Switch to --api-sock so the socket stays open and reachable after the guest starts, instead of driving everything through a static config file. Signed-off-by: Anamika AggarwaL <anamikaagg18@gmail.com>
Anamika1608
force-pushed
the
firecracker-api-sock
branch
from
691f601 to
811a606
Compare
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
1 participant
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.
Related to #112.
Today Firecracker boots via
--no-api --config-file, which explicitly disables its control socket. This switches to--api-sock, so the socket stays open and reachable after the guest starts, instead of everything being driven through a static config file.This is a minimal first step: the JSON config file is still generated the same way, only the launch flag changes.