Skip to content
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

ERROR: Failed to map /geth: Resource busy #849

Open
zhq9695 opened this issue Oct 26, 2021 · 0 comments
Open

ERROR: Failed to map /geth: Resource busy #849

zhq9695 opened this issue Oct 26, 2021 · 0 comments
Labels
needs-triage Bug does not yet have a priority assigned

Comments

@zhq9695
Copy link

zhq9695 commented Oct 26, 2021

I use ethereum client "geth" inside the sgx-lkl, but it can't work.

I built a docker container to run the geth, it can work.

I use the following cmd to create sgx-lkl image:

sgx-lkl-disk create --docker=eth --size=2000M eth.img
sgx-lkl-cfg create --disk eth.img
sgx-lkl-run-oe --host-config=host-config.json --enclave-config=enclave-config.json --sw-debug

but it can't work, and showed the following error:

[ SGX-LKL ] WARN: disabling fsgsbase in sw-debug mode, despite it being enabled in enclave config.
[[ SGX-LKL ]] ERROR: Failed to map /geth: Resource busy
[ 0.079782] reboot: Restarting system

Could you please tell me why it can't work ? what's the reason of this error ?

@github-actions github-actions bot added the needs-triage Bug does not yet have a priority assigned label Oct 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Bug does not yet have a priority assigned
Projects
None yet
Development

No branches or pull requests

1 participant