Skip to content

feat(firecracker): launch with control socket instead of config file#809

Open
Anamika1608 wants to merge 3 commits into
urunc-dev:mainfrom
Anamika1608:firecracker-api-sock
Open

feat(firecracker): launch with control socket instead of config file#809
Anamika1608 wants to merge 3 commits into
urunc-dev:mainfrom
Anamika1608:firecracker-api-sock

Conversation

@Anamika1608

Copy link
Copy Markdown

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.

@netlify

netlify Bot commented Jul 8, 2026

Copy link
Copy Markdown

Deploy Preview for urunc ready!

Name Link
🔨 Latest commit 9b4f4ff
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6a51f3b657b90d0008c68304
😎 Deploy Preview https://deploy-preview-809--urunc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

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 Anamika1608 force-pushed the firecracker-api-sock branch from 691f601 to 811a606 Compare July 8, 2026 10:09
Add an optional socket_path field under a monitor's configuration
section so users can override where the control socket is created.
Falls back to today's default path when unset. The field is added to
the shared MonitorConfig type, so it is available to any monitor, but
only Firecracker's BuildExecCmd reads it in this change, since it is
the only monitor with a control socket right now.

Signed-off-by: Anamika AggarwaL <anamikaagg18@gmail.com>
Add the new socket_path field to the Monitor Options table and the
Firecracker example, matching the existing style for path/data_path.

Signed-off-by: Anamika AggarwaL <anamikaagg18@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant