Skip to content

Commit 4050d66

Browse files
committed
tee: Describe I/O error troubleshooting when launching debug enclaves
1 parent b5bfc0a commit 4050d66

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

docs/node/run-your-node/prerequisites/set-up-trusted-execution-environment-tee.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -546,6 +546,26 @@ This may be related to a bug in the Linux kernel when attempting to run enclaves
546546
on certain hardware configurations. Upgrading the Linux kernel to a version
547547
equal to or greater than 6.5.0 may solve the issue.
548548

549+
### Unable to Launch Enclaves: Input/output error
550+
551+
If running `sgx-detect --verbose` reports:
552+
553+
```
554+
🕮 SGX system software > Able to launch enclaves > Debug mode
555+
The enclave could not be launched.
556+
557+
debug: failed to load report enclave
558+
debug: cause: Failed to call ECREATE.
559+
debug: cause: I/O ctl failed.
560+
debug: cause: Input/output error (os error 5)
561+
```
562+
563+
This may be related to a bug in the [`rust-sgx`](https://github.com/fortanix/rust-sgx/issues/565)
564+
library causing `sgx-detect` (and `attestation-tool`) to fail and report that
565+
debug enclaves cannot be launched. This is a known issue and is being worked on.
566+
If the `sgx-detect` is reporting that production enclaves can be launched, you
567+
can ignore this error when setting up the Oasis node.
568+
549569
### Couldn't find the platform library
550570

551571
If AESMD service log reports:

0 commit comments

Comments
 (0)