Installation Steps #583
Comments
|
Hi there,
|
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
go version go1.21.2 linux/arm64
N: Unable to locate package edglessrt
N: Unable to locate package edglessrt
E: No packages found
c33669b10382afad721d2dd534504dbcfff125df
|
|
Hi @dhruvinparikh |
|
It was installed but not sure why it isn't showing up in apt, I think was the issue. Looking into it. Will update |
|
When we build the Coordinator control plane and Marble test applications: mkdir build I am stuck at make with the following error: runtime/cgogcc_arm64.S: Assembler messages: |
Are you trying to build MarbleRun on an ARM host? In the second case, unset the |
|
uname -a I tried following unset GOARCH make but still same error [ 0%] Built target coordinator-noenclave |
|
Hi, can you please provide the full terminal output of all these commands |
|
root@d1cc01526652:/com.docker.devenvironments.code/marblerun# mkdir build && cd build Add the installation prefix of "OpenEnclave" to CMAKE_PREFIX_PATH or set -- Configuring incomplete, errors occurred! |
|
updated my comment to include the source command |
|
Works, thanks! |
|
Actually sorry, need to unclose this for a second. There was an error at the end we missed. Updated terminal log The error: ' make: *** [Makefile:91: all] Error 2 ' It looks like we're close but something may be missing. |
|
It seems it doesn't (even try to) sign the coordinator-enclave binary. We have |
|
|
Is the git working tree clean or did you change any file? After getting this error, try what happens if you run |
|
Following are the last few lines after running |
|
Inside getting following messages on console OE_SIMULATION=1 erthost coordinator-enclave.signed
[erthost] running in simulation mode
[erthost] loading enclave ...
[erthost] entering enclave ...
[meshentry] invoking premain
[meshentry] invoking main
{"level":"info","ts":1711388126.5188923,"caller":"coordinator/run.go:40","msg":"Starting coordinator","version":"1.4.1","commit":"c916af2d1592717d4e455e22fc663a0cc700a111"}
{"level":"info","ts":1711388126.5188923,"caller":"coordinator/run.go:73","msg":"Creating the Core object"}
{"level":"info","ts":1711388126.5228922,"caller":"core/core.go:124","msg":"Loading state"}
{"level":"info","ts":1711388126.5228922,"caller":"core/core.go:162","msg":"No sealed state found. Proceeding with new state."}
{"level":"info","ts":1711388126.5228922,"caller":"core/core.go:289","msg":"Generating quote"}
ERROR: can't get report in simulation mode (oe_result_t=OE_UNSUPPORTED) [openenclave-src/enclave/sgx/report.c:oe_get_report_v2:190]
{"level":"warn","ts":1711388126.5228922,"caller":"core/core.go:293","msg":"Failed to get quote. Proceeding in simulation mode.","error":"OE_UNSUPPORTED"}
{"level":"info","ts":1711388126.5228922,"caller":"coordinator/run.go:102","msg":"Starting the client server"}
{"level":"info","ts":1711388126.5228922,"caller":"coordinator/run.go:111","msg":"Starting the marble server"}
{"level":"info","ts":1711388126.5228922,"caller":"server/server.go:121","msg":"Starting client https server","address":":4433"}
{"level":"info","ts":1711388126.5228922,"caller":"grpclog/component.go:36","msg":"[core][Server #1] Server created","system":"grpc","grpc_log":true}
{"level":"info","ts":1711388126.5228922,"caller":"grpclog/component.go:36","msg":"[core][Server #1 ListenSocket #2] ListenSocket created","system":"grpc","grpc_log":true}
{"level":"info","ts":1711388126.5228922,"caller":"coordinator/run.go:123","msg":"Started gRPC server","grpcAddr":"[::]:2001"} |
|
make and coordinator output both look good |
|
@thomasten wondering if you can take a look at this. Wondering what exit code 128 is and if this is an issue that is affecting our build?
[+] Building 5.3s (6/10) docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 2.87kB 0.0s => [internal] load metadata for ghcr.io/edgelesssys/marblerun/build-base:v1.4.1 0.1s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [build 1/5] FROM ghcr.io/edgelesssys/marblerun/build-base:v1.4.1@sha256:f00b8652db5ccc88832df06450cd10e6d2846934c72675a929666cac331852de 0.0s => CACHED [build 2/5] RUN apt-get install -y --no-install-recommends build-essential ca-certificates clang-11 cmake git libssl-dev ninja-build wget 0.0s => ERROR [build 3/5] RUN wget -qO- https://go.dev/dl/go1.21.8.linux-amd64.tar.gz \| tar -C /usr/local -xz && git clone -b v0.4.3 --depth=1 https://github.com/edgelesssys/edgelessrt 5.1s------ > [build 3/5] RUN wget -qO- https://go.dev/dl/go1.21.8.linux-amd64.tar.gz \| tar -C /usr/local -xz && git clone -b v0.4.3 --depth=1 https://github.com/edgelesssys/edgelessrt && git clone -b v1.5.0 --depth=1 https://github.com/edgelesssys/marblerun && mkdir ertbuild mrbuild:3.415 Cloning into 'edgelessrt'...3.791 Note: switching to 'b49e0175599ad3deae43eb69a52e1784d1a12f20'.3.7913.791 You are in 'detached HEAD' state. You can look around, make experimental3.791 changes and commit them, and you can discard any commits you make in this3.791 state without impacting any branches by switching back to a branch.3.7913.791 If you want to create a new branch to retain commits you create, you may3.791 do so (now or later) by using -c with the switch command. Example:3.7913.791 git switch -c 3.7913.791 Or undo this operation with:3.7913.791 git switch -3.7913.791 Turn off this advice by setting config variable advice.detachedHead to false3.7913.821 Cloning into 'marblerun'...3.958 warning: Could not find remote branch v1.5.0 to clone.3.958 fatal: Remote branch v1.5.0 not found in upstream origin------Dockerfile:17-------------------- 16 \| ARG goversion=1.21.8 17 \| >>> RUN wget -qO- https://go.dev/dl/go${goversion}.linux-amd64.tar.gz \| tar -C /usr/local -xz \ 18 \| >>> && git clone -b $erttag --depth=1 https://github.com/edgelesssys/edgelessrt \ 19 \| >>> && git clone -b $mrtag --depth=1 https://github.com/edgelesssys/marblerun \ 20 \| >>> && mkdir ertbuild mrbuild 21 \|--------------------ERROR: failed to solve: process "/bin/sh -c wget -qO- https://go.dev/dl/go${goversion}.linux-amd64.tar.gz \| tar -C /usr/local -xz && git clone -b $erttag --depth=1 https://github.com/edgelesssys/edgelessrt && git clone -b $mrtag --depth=1 https://github.com/edgelesssys/marblerun && mkdir ertbuild mrbuild" did not complete successfully: exit code: 128
--
|
|
The dockerfiles in the master branch are for an upcoming release. You can use the ones at tag v1.4.1: https://github.com/edgelesssys/marblerun/tree/v1.4.1/dockerfiles |
|
I think we're right near the end then: when we run make we get this error: 0%] Built target coordinator-noenclave |
|
Here are the full steps we are following and where we get stuck: Ego installation sudo mkdir -p /etc/apt/keyrings Verify ego installation https://github.com/edgelesssys/ego.git OE_SIMULATION=1 ego run helloworld Install edgelessrt sudo mkdir -p /etc/apt/keyrings sudo apt update . /opt/edgelessrt/share/openenclave/openenclaverc Check edglessrt installation apt show edglessrt git clone https://github.com/edgelesssys/edgelessrt.git make OE_SIMULATION=1 erthost enclave.signed Install go cd ~ Install Docker sudo apt-get update Build marble run git clone --branch v1.4.1 https://github.com/edgelesssys/marblerun.git That's when we get the above error |
|
The docker build and the direct build in your host environment are alternatives. You don't need both. From your commands, I'd assume that the direct build on the host fails. Let's ignore this for a moment and look at the docker build. So when running Does this command succeed? Does it create the binaries in the current working dir? |
|
That worked. But still getting the same error with make. |
|
The problem seems to be that this commit can't be built with latest EdgelessRT and Go. You can use EdgelessRT 0.4.2 and Go 1.20.14 or build latest master of MarbleRun instead. |
The step we're following to install are here : https://github.com/edgelesssys/marblerun/blob/master/BUILD.md#build
The text was updated successfully, but these errors were encountered: