Dramelac

Hello, Indeed Exegol does not seem to be the cause of your problem with responder... Concerning the resolv.conf, the file is automatically synchronized between the host and the container when...

Hello, Indeed it's a known issue but we are already using the latest docker library, there is an issue opened https://github.com/docker/docker-py/issues/2902 But the lib appears to not be maintained by...

Yes indeed ! Now we just have to wait for them to release a new version of the lib. I'll close the ticket once the new version will be released...

Hello, First, thank you for your report! This error is not related to the exegol image, it seems like your docker VM cant find the `/tmp/.X11-unix` socket. It's weird because,...

@ShutdownRepo do you think we could check the docker desktop configuration from the wrapper? A bit like the configuration check for XQuartz? In any case it will be necessary to...

Either we find a way (environment variable, config file, system command, ...) to check this configuration before the creation of the container to add a safe check in the wrapper,...

Hello, Thank you for your feedback, Indeed this problem is one of the areas of improvement of Exegol ( through many other topics) but it is not currently planned to...

I pushed in dev branch a first implementation of the permission sharing between exegol and the host. It needs some testing before closing this issues and the latest `nightly` image...

Indeed it's strange, did you modify something on your host? Could you do the following tests? - `ls -la /etc/timezone` - `exegol info ` - `docker inspect ` Thank you!

It seems that your `tzdata` (or equivalent) package has been updated since the creation of your container, leading to the modification of your `/etc/localtime` file The strange behavior is that...