-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WeTEE Network Milestone 2 Delivery #1119
Conversation
Hi, I'll evaluate this milestone. @keeganquigley could you please assign it to me? |
Hi @BurnWW, I tried to install the software using these instructions but I'm having an error while running I'm using an Intel 7th gen CPU and Ubuntu 20.04. I ran
Can you help with that? I'm using the go version |
Thank you @dsm-w3f , I have already fully understood the problem. sudo apt remove golang
# Install golang 1.20 ,ubuntu 20.04 default golang version is 1.13, is too low
sudo apt install golang-1.20
# set golang env, also you can add it to .bashrc file(in home dir) or .zshrc file(in home dir)
export GOROOT=/usr/lib/go-1.20/
export PATH=$PATH:$GOROOT/bin We have also checked recent updates to the code and made the following updates in the documentation:
After updating golang, please update the worker’s code and execute the following command.
|
@BurnWW thanks for the answer. I tried again, but is not working yet. This is the Go language version that I'm using currently. I installed it using snap.
When I try to run without docker I got this error:
When I tried to run with docker I got this other one
Can you assist with these problems? |
Thank you @dsm-w3f , I have already fully understood the problem.
This error occurs because the Golang version defined in our go.mod file is 1.20, and executing
This issue is caused by the incomplete installation of ego and SGX SDK on the host machine. sudo apt install build-essential libssl-dev
sudo mkdir -p /etc/apt/keyrings
wget -qO- https://download.01.org/intel-sgx/sgx_repo/ubuntu/intel-sgx-deb.key | sudo tee /etc/apt/keyrings/intel-sgx-keyring.asc > /dev/null
echo "deb [signed-by=/etc/apt/keyrings/intel-sgx-keyring.asc arch=amd64] https://download.01.org/intel-sgx/sgx_repo/ubuntu $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/intel-sgx.list
sudo apt update
EGO_DEB=ego_1.4.1_amd64_ubuntu-$(lsb_release -rs).deb
wget https://github.com/edgelesssys/ego/releases/download/v1.4.1/$EGO_DEB
sudo apt install ./$EGO_DEB build-essential libssl-dev After the installation is completed, executing $ cpuid -1 -l 0x7 |grep SGX
SGX: Software Guard Extensions supported = true
SGX_LC: SGX launch config supported = true
$ sudo ls /dev/sgx
enclave provision |
Hi @BurnWW thanks for the improvements. I tried again but look like that my CPU doesn't support one of the features needed to run the software. When I ran the command below I got a different answer than the expected.
I'll try to run it using some cloud service. Do you already tried this approach? Do you recommend some of them? It looks like that Microsoft has one that supports SGX. |
@dsm-w3f I’m truly sorry that we haven’t fully researched the support of intel 7th cpu for the ego program, which has caused inconvenience to your verification process. After checking, we found out that SGX FLC is supported starting from intel 8th generation processors, and we have already corrected the documentation accordingly. I will go back to investigate the cloud service and provide you with the test results as soon as possible. Once again, please accept my apologies. |
hello @dsm-w3f, I’ve conducted a comprehensive research on the Azure operating environment, and I found that Azure fully meets the requirements for software debugging and usage.
This is the configuration for the virtual machine I created.
This is the result of my test in azure DC2s_v2 virtual machine. |
hello @dsm-w3f, Due to the inability to directly use https://polkadot.js.org/apps for debugging non-https blockchain nodes in a cloud-based debugging environment, I am providing a copy of the http version of Polkadot UI for convenient debugging at http://polkadot-ui.tc.asyou.me/. |
Hi @BurnWW, thanks for the explanation. I set up a virtual machine in Azure with the same type of instance that you did. I was able to run the installation instructions. However, in the last step, when running without docker, I received this logs, which indicate that something is not ok. Could you assist with that? Is this in a state that I can proceed with the tests?
I ran with docker and got a different error, see the logs below:
|
@dsm-w3f I see that you have already run the program, and there’s an error in the expression of this debug log:
I’ve replaced it with About docker run logs
We haven’t encountered this error before. Would it be convenient to open a Matrix channel so that we can quickly understand and resolve the issue? If possible, please join the channel below. https://matrix.to/#/!yRyTqmQdvbcHCtMIHa:matrix.org?via=matrix.org |
hello @dsm-w3f, I reproduced this issue by reinstalling the environment.
I have update new docker image, The solution can be achieved by following these steps. docker pull wetee/worker:dev
docker run --device /dev/sgx/enclave --device /dev/sgx/provision \
--network host \
-e KUBECONFIG=/etc/kube/config \
-v /etc/rancher/k3s:/etc/rancher/k3s \
wetee/worker:dev |
@dsm-w3f thank you for your opinion.
The problem has been well resolved and will no longer result in execution errors due to golang version issues.
Here we will provide a better testing method; currently,i have push new docker image
There is not a particularly strong connection between the two projects, which is due to the fact that the test document was not thoroughly reviewed, leading to elementary errors.
In this case, nginx is an example written in C language, and I will provide examples of both C++ programs and Python programs. |
@dsm-w3f Thank you very much, this is a significant oversight. c https://github.com/wetee-dao/examples/tree/main/gramine-c All the issues have now been resolved, and testing can continue. If any further problems arise, we will respond immediately. |
@BurnWW thank you for the improvements and fixes. I checked again and the milestone is accepted from my site. Just a small issue with the docker that could be fixed but don't prevent the acceptance of the milestone. See details in the evaluation PR. Thanks for the collaboration, great job! @keeganquigley the PR with the evaluation is open and updated. |
Thanks for the quick fixes @BurnWW your evaluation was accepted and I hereby pass this milestone. Nice work! |
🪙 Please fill out the invoice form in order to initiate the payment process. Thank you! |
@dsm-w3f hello, I have investigated the cause of the warning in detail.
A more specific warning has been found through adjustment. this warning is generated by gramine, and it exists in all gramine official cases. I will continue to pay attention to and follow up this warning |
hi @BurnWW we sent the payment today |
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#2065