This repository has been archived by the owner on May 12, 2021. It is now read-only.
Hypervisor process may be left running if startSandbox fails #1636
Comments
marcov
added a commit
to marcov/kata-runtime
that referenced
this issue
May 8, 2019
Make sure the hypervisor is stopped if startSandbox does not succeed, by calling stopSandbox. Fixes: kata-containers#1636 Signed-off-by: Marco Vedovati <[email protected]>
marcov
added a commit
to marcov/kata-runtime
that referenced
this issue
May 16, 2019
Make sure the hypervisor is stopped if startSandbox does not succeed, by calling stopSandbox. Fixes: kata-containers#1636 Signed-off-by: Marco Vedovati <[email protected]>
marcov
added a commit
to marcov/kata-runtime
that referenced
this issue
May 16, 2019
Make sure the hypervisor is stopped if startSandbox does not succeed, by calling stopSandbox. Fixes: kata-containers#1636 Signed-off-by: Marco Vedovati <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I did some tests running a container with firecracker. I encountered a situation where kata-runtime would exit with an error message, yet the firecracker process was left running.
In my case the failure was due to a misconfiguration (the firecracker binary I used wasn't built with vsock support); yet in similar situations the hypervisor should not be left running.
The text was updated successfully, but these errors were encountered: