Closed Doplgamer closed 1 week ago
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) New release very soon to address this bug.
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