iberpal-skeleton is constantly being updated, it may not be compatible with the previous images.

 Signed-off-by: Shirong Hao shirong@linux.alibaba.com

Signed-off-by: NShirong Hao <shirong@linux.alibaba.com>

- Add Dragonwell and Skeleton images in reference container image
- Update Version number
Signed-off-by: NShirong Hao <shirong@linux.alibaba.com>

- Update centos version from 7.5 to 8.1
- Update occlum version from 0.14.0 to 0.15.1
- Update the way to Install SGX SDK and SGX PSW
- Update tht value of ENCLAVE_RUNTIME_ARGS
Signed-off-by: NShirong Hao <shirong@linux.alibaba.com>

Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

- Use liberpal-skeleton to replace liberpal-skeleton.so in README.
- Use liberpal-skeleton-v1.so to replace liberpal-skeleton.so in rune/libcontainer/specconv/example.go
- Use liberpal-skeleton*.so to repalce liberpal-skeleton.so in rune/Makefile and .gitignore
Signed-off-by: NShirong Hao <shirong@linux.alibaba.com>

Use liberpal-skeleton-v${SKELETON_PAL_VERSION}.so to replace liberpal-skeleton.so in README.
Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

SGX in-tree driver has a different way to go agains SGX out-of-tree
driver. The enclave range is mapped to EPC memory after executing
EINIT, so the anonymous mapping occupying enclave range must be done
early instead of creating it based on the fd of /dev/isgx.
Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>

Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>

Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>

- Add docs/running_rune_with_occlum_bundle.md
- Remove docs/running_rune_with_docker.md
- Update skeleton README.md to add way to run rune with skeleton bundle
- Update README.md of inclavare-containers
- Add docs/running_rune_with_occlum.md
Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

1. Add way to build and install rune.
2. Add way to configure rune to Docker runtimes.
Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>

Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>

This new implementation inspires the design of https://github.com/jsakkine-intel/linux-sgx/tree/next/tools/testing/selftests/x86/sgx, which is a real enclave runtime.
Signed-off-by: Njack.wxz <wangxiaozhe@linux.alibaba.com>

inclavare-containers is a set of tools for running trusted
applications in containers with the hardware-assisted enclave
technology. Enclave, referred to as a protected execution
environment, prevents the untrusted entity from accessing the
sensitive and confidential assets in use.

Currently, inclavare-containers consists of two core components:
rune and enclave runtime.

rune is a CLI tool for spawning and running enclaves in containers
according to the OCI specification. The codebase of rune is
a fork of runc, so rune can be used as runc if enclave is not
configured or available.

Enclave runtime is the backend of rune, which is responsible
for loading and running applications inside enclaves. The
interface between rune and enclave runtime is Enclave Runtime PAL
API, which allows invoking enclave runtime through well-defined
functions. The software for confidential computing may benefit
from this interface to interact with OCI runtime.

Additionally, this commit includes additional information about the
use of inclavare-containers.
- Run sample enclave runtime skeleton with rune
- Run enclave runtime Occlum with rune

See README.md for more details.
Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>
Signed-off-by: NXiaozhe Wang <wangxiaozhe@linux.alibaba.com>
Signed-off-by: NYilin Li <YiLin.Li@linux.alibaba.com>