anjuna-fs-proxy
A daemon that provides an Anjuna Nitro enclave access to basic mount volumes on the VM host
filesystem for persistent storage.
DESCRIPTION
anjuna-fs-proxy must be run prior to starting an enclave with one or more basic volumes
defined in its configuration.
The anjuna-fs-proxy daemon mounts a directory on the host VM filesystem to one or more
mount points inside the enclave.
The enclave can read and write to these mount points using normal filesystem operations.
For an enclave using basic mounts to work properly,
it is important to run anjuna-fs-proxy before starting the enclave.
In order to clean up resources when you terminate an enclave,
you should kill the anjuna-fs-proxy after terminating an enclave.
When restarting an enclave,
it is important to stop and start anjuna-fs-proxy as described above.
|
OPTIONS
Usage: anjuna-fs-proxy [Options] Options: --daemonize Run it as daemon (default: off) --verbose log debug message (default: off) --syslog log debug messages in syslog (default: off) --anjunafs-rootdir the root directory from where the anjunafs read the unencrypted files
EXAMPLE
To use anjuna-fs-proxy,
you also need to define the basic-type mounts in the enclave configuration file.
For example,
if you want to mount the files from /home/static and /home/logs into the enclave at
/shared/static and /var/app/logs,
you would add the following to your enclave configuration file:
mounts:
- name: static # the name within your anjunafs-rootdir
type: basic # anjuna-fs-proxy uses the `basic` type
mountPath: /shared/static # the path within your enclave
- name: logs
type: basic
mountPath: /var/app/logsAnd you would start anjuna-fs-proxy with the anjunafs-rootdir like this:
$ anjuna-fs-proxy --daemonize --anjunafs-rootdir /home