Persistent Storage Overview
The Anjuna Nitro Runtime provides a seamless experience for running Nitro Enclaves with persistent storage. This section describes the persistent storage options that the Anjuna Nitro Runtime supports and describes setting up a Nitro Enclave with persistent storage.
Volume mounts & Bind mounts
The Anjuna Nitro Runtime provides two ways of storing persistent data: volume mounts and bind mounts. Both options look the same from within the enclave and provide a persistent mount point.
Volume mounts allow persisting data inside an enclave, and they are more performant than bind mounts. Volume mounts are created and managed by the Anjuna Nitro Runtime. Volume mounts are persistent, and the data is saved on the parent host. However, only an enclave can access the contents of the volume mount, and the parent host cannot mount that volume when it’s in use by an enclave. You can create multiple volume mounts with different sizes. A single enclave can mount a maximum of 1 volume at a time.
Volume mounts are under active development and considered experimental. |
Bind mounts allow binding a file or a directory and its contents from the parent host into an enclave. It is less performant compared to volume mounts but does not require creating a dedicated volume.