-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
firecracker-containerd in-VM agent is not responsive after snapshot creation when using vanilla firecracker setup #818
Comments
Please provide details and comment on the severity of the issue. |
ClarificationEven though firecracker-containerd's in-VM agent does not respond, the container running inside the VM works fine and is responsive. SeveritySince firecracker-containerd's in-VM agent does not respond, forceful termination of the VM is required. As a consequence, some containerd resources are leaked (the container and the container snapshot, at least). AFAIC, cleaning up the resources requires the regular cleanup procedure to succeed, i.e., killing the task, deleting the task, and deleting the container — the resources are held by them: Lines 246 to 265 in 899893a
I am not aware of a procedure to forcefully delete the task and the container (as the procedure described above hangs on the first step). The reset procedure via |
@ustiugov may be related firecracker-microvm/firecracker#4099. |
Describe the bug
After a VM snapshot is created, the firecracker-containerd in-VM agent stops responding:
forcefully terminated VM
error.The text was updated successfully, but these errors were encountered: