You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
Status endpoint currently provides IP address in case enclave starts up but doesn't really provide any reason in case enclave fails to start. It would help users if a reason was provided in case enclave fails, it can be due to enclave image url is not reachable or enclave image downloaded is corrupted, not enough CPUs, not enough memory and so on. This is especially useful when users are trying to figure an optimal resource allocation by manually setting memory.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Status endpoint currently provides IP address in case enclave starts up but doesn't really provide any reason in case enclave fails to start. It would help users if a reason was provided in case enclave fails, it can be due to enclave image url is not reachable or enclave image downloaded is corrupted, not enough CPUs, not enough memory and so on. This is especially useful when users are trying to figure an optimal resource allocation by manually setting memory.
The text was updated successfully, but these errors were encountered: