Closed wem-r closed 1 year ago
Hello,
Thank you for pointing out this error, I hadn't thought of it! I'll fix it in a future version (probably by not allowing the creation of containers with the same name on OSes that don't support the distinction correctly).
Fixed in 2b449bbe
Describe the bug
Hello There!
While debugging another Exegol issue (unrelated to this one) that I have, I discovered a bug that prevents me from starting or removing an existing container.
What I think is the reason :
Container creation is case insensitive (you can create
Test
andtest
) but the host file system might not be.Egexol do not warn you that an image already exists with that name, regardless of casing.
Even tho
exegol info
will list the two containers, only 1 workplace will be created(See steps to reproduce first)
Since removing
Test
deleted~/.exegol/workspaces/Test
, the remaining containertest
cannot be started anymore, nor can it be deleted, because the workplace directory do not exist anymore. I don't think it's really needed, but as asked, I pasted the execution logs bellow.This is only an issue on file systems that are case sensitve. By that I mean FS that prevents you to have two directory with the same name with different casing.
A few exemples
on widows:
NTFS is case sensitive = issue
or MacOS
By default MacOS uses APFS, which is case sensitive = issue
This is not a problem on FS that are case-insensitive
I tested on Kali (EXT4) , Kaisen (BTRFS) and Manjaro (EXT4)
System configuration
MacOS Ventura 13.4 (M2 Pro MBP)
Python 3.11.3
Steps To Reproduce
exegol start test
(doesn't matter which image)exit
(no need to do anything specific in it)exegol start Test
exit
I now have the two containers
exegol remove Test
Exegol Wrapper Version
Host OS
MacOS
Execution logs in debug mode
Anything else?
Manual fix
This is what I've done to manually fix this for me:
mkdir ~/.exegol/workspaces/Test
I need to mention that I've not been using Exegol for an extensive period of time, so there may be a "native" way to address this issue that I'm not yet familiar with.
I don't know if opening a GH issue was really needed, or if it's just because I'm not using it correctly. So please, let me know if there are any specific documentation that cover this issue, any recommended steps within Exegol to mitigate the problem, or if you need any more informations.
In any case (pun itended), thx in advence.