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
Hello, an issue came up when working on a project built on top of a Nitro VM: when the enclave is terminated the functionality that would be present in a regular docker container is not present in Nitro as the VM gets powered off immediately. Thus things like flushing unwritten data in disc cache for example don't exist.
Is there a way to have the Nitro infrastructure do a clean shutdown of the enclave’s virtual machine instead of just immediately powering it off, or maybe have some sort of hook logic placed that will execute user-specific code inside an enclave before the VM shuts down? If not present can this feature potentially be added?
The text was updated successfully, but these errors were encountered:
Hello, an issue came up when working on a project built on top of a Nitro VM: when the enclave is terminated the functionality that would be present in a regular docker container is not present in Nitro as the VM gets powered off immediately. Thus things like flushing unwritten data in disc cache for example don't exist.
Is there a way to have the Nitro infrastructure do a clean shutdown of the enclave’s virtual machine instead of just immediately powering it off, or maybe have some sort of hook logic placed that will execute user-specific code inside an enclave before the VM shuts down? If not present can this feature potentially be added?
The text was updated successfully, but these errors were encountered: