on host, not docker, if host is ubuntu 22.04:
cargo build --release --features=skip-extrinsic-filtering
https://github.com/integritee-network/integritee-dev/tree/main/worker
to re-enter docker later:
docker start -ai integritee-dev-worker-and-node
or if you NEED root access
docker exec -it integritee-dev-worker /bin/bash
build and run teeracle:
same as above
build and run validateer:
docker run --name integritee-dev-worker -it --expose 9944-9999 -p 2000:2000 -v $(pwd):/home/ubuntu/worker -e MYUID=$(id -u) -e MYGUID=$(id -g) integritee/integritee-dev:0.2.2 /bin/bash
find out host ip:
ip addr show docker0 | grep -Po 'inet \K[\d.]+'
use this IP address when calling the worker
replace MRENCLAVE with yours
second worker requests provisioning in same container:
or, alternatively, just starts running and obtains provisioning on the fly:
in integritee/parachain:
spawn rococo-local with asset hub and integritee
zombienet-linux-x64 spawn --provider native zombienet/rococo-local-with-integritee-and-asset-hub.toml
start worker with target-b AssetHub setup
the client now needs to connect to to either integritee or target_a depending on the activity
screencast hints:
new terminal:
then, start validateer and wait until ProxyAdded appears on AssetHub
reasonable logging level for worker and cli:
browsers are very restrictive, even for localhost.
We need to use https for localhost or the browser will refuse to connect to the enclave with wss
THIS WORKS BUT DOES NOT SOLVE THE PROBLEM
the browser can connect to https://localhost, but the ws won't open anyway
then
manually change these lines and run yarn test
with the worker running in docker:2000 and the node running on host:9944
caveat: each new build of the worker needs a change of MRENCLAVE