# Teaclave Docker
This directory contains the docker infrastructure for build and runtime environment. Note that you must mount SGX device and ASEM domain socket into the container environment to use SGX feature.
The build dockerfile (
build.*.Dockerfile) only contains minimal dependencies
to build and test the project. To use them, you can directly use pre-built
docker images from Docker Hub with:
$ docker run --rm \ --device=/dev/isgx \ -v/var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket \ -v`pwd`:/teaclave \ -w /teaclave \ -it teaclave/teaclave-build-ubuntu-1804-sgx-2.9:latest \ /bin/bash
or you can also build the image by yourself with
$ docker build -t teaclave-build - < build.*.Dockerfile
$ docker run --rm \ --device=/dev/isgx \ -v/var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket \ -v`pwd`:/teaclave \ -w /teaclave \ -it teaclave/teaclave-build \ /bin/bash
Teaclave contains many services, we put services, config and related
resources into one docker image
teaclave-rt.ubuntu-1804.Dockerfile). To make the deployment
simpler, we recommend to use docker-compose
to manage all services. Since the remote attestation is required for all
services, you should setup the attestation service configurations
before start the services. You can use env vars or set them in the
Here is an example to start all services.
$ export AS_SPID="00000000000000000000000000000000" $ export AS_KEY="00000000000000000000000000000000" $ export AS_ALGO="sgx_epid" $ export AS_URL="https://api.trustedservices.intel.com:443" $ ./run-teaclave-services.sh Starting teaclave-file-service ... done Starting teaclave-authentication-service ... done Starting teaclave-access-control-service ... done Starting teaclave-scheduler-service ... done Starting teaclave-management-service ... done Starting teaclave-execution-service ... done Starting teaclave-frontend-service ... done Attaching to ...
Note that the
teaclave-file-service container is a simple http server for
demonstrating our examples. You can disable it and use other cloud file system
like S3 instead for registering input/output files.