-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Failure to get Exegol info #238
Comments
same same |
Hello everyone. Thanks for reporting this issue. We are aware of it and are working on a quick fix. This only impacts the exegol info command. Containers can still be launched via the exegol start command. |
You can use the --offline flag with the command to avoid the stacktrace in the meantime |
This issue has been fixed in the latest dev version (for those using a git clone install) |
Describe the bug
Tried to get Exegol info and get faced with an error
Steps To Reproduce
exegol info
Exegol Wrapper Version
Host OS
None
Configuration of the concerned container
No response
Execution logs in debug mode
Exception
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: