mirror of
https://github.com/clearlinux/graphene.git
synced 2026-06-28 08:55:54 +00:00
Michał Kowalczyk
e587869e13
Supporting these options complicates the design of Graphene and loading
logic significantly, providing little useful functionality:
- loader.exec:
- the main user of it were our tests
- worked only for the first process spawned inside Graphene, as it
was a unidirectional manifest->binary mapping, so the child
process didn't know about the corresponding manifest.
- sgx.sigfile:
- probably all existing usages of it were completely redundant
- was resolved relatively to CWD instead of the executable location,
which made it mostly useless
From now on, the correct location of the files is:
- either place the manifest and sigfile next to the binary, with a
matching name, or
- create a symlink to the binary in the folder where manifests are
stored and launch it through this symlink
Node.js
This directory contains a Makefile and template manifest to run Node.js on Graphene. We tested it with Node.js 8.10.0 on Ubuntu 18.04. This example uses Node.js installed on the system instead of compiling from source as some of the other examples do.
The Makefile and the template manifest contain comments to hopefully make them easier to understand.
Quick Start
To run the regression test execute make check. To do the same for SGX, execute make SGX=1 check.