You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've been trying to use firecracker's snapshot and restore functionality, but one of the challenges is that the current version of the Firecracker Go SDK doesn't support loading from a snapshot. It does integrate well with CNI and has been setting up IPs and adapters really well.
So one workaround appears to be to use HTTP requests to the unix socket to restore a snapshot taken with the Go SDK. The only outstanding issue is getting a stable tap device name, otherwise Firecracker panics when trying to load the snapshot either with no output at all, or the equivalent of "tap not found".
What would you suggest? Is there a way to do this, or is CNI not suited to this task due to the way it allocates tap names? Could the tap name be passed in or configured from some other metadata from the host-local / ptp plugin?
Hi, I've been trying to use firecracker's snapshot and restore functionality, but one of the challenges is that the current version of the Firecracker Go SDK doesn't support loading from a snapshot. It does integrate well with CNI and has been setting up IPs and adapters really well.
So one workaround appears to be to use HTTP requests to the unix socket to restore a snapshot taken with the Go SDK. The only outstanding issue is getting a stable tap device name, otherwise Firecracker panics when trying to load the snapshot either with no output at all, or the equivalent of "tap not found".
What would you suggest? Is there a way to do this, or is CNI not suited to this task due to the way it allocates tap names? Could the tap name be passed in or configured from some other metadata from the host-local / ptp plugin?
@Kern-- @kzys
The text was updated successfully, but these errors were encountered: