Closed KayZ-Safeit closed 11 months ago
Hello @KayZ-Safeit Did you follow all the requirements from the docs when installing Exegol for Windows ? https://exegol.readthedocs.io/en/latest/getting-started/install.html
Yes, I followed every steps
Ok, can you run the command cmd.exe /c ver
inside your WSL2 shell and copy/paste or screenshot the result ?
jt@DESKTOP-EUI8PI0:~$ cmd.exe /c ver -bash: /mnt/c/Windows/system32/cmd.exe: cannot execute binary file: Exec format error
It looks like there is a problem with systemd
It looks like there is a problem with systemd
Indeed, i don't know WSL enough to debug but i found this thread: https://github.com/microsoft/WSL/issues/9146
Maybe try sudo update-binfmts --disable cli
and run cmd.exe /c ver
again ?
jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ sudo update-binfmts --disable cli jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ cmd.exe -bash: /mnt/c/Windows/system32/cmd.exe: cannot execute binary file: Exec format error jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ sudo update-binfmts --disable-cli update-binfmts: unrecognized option '--disable-cli' Try 'update-binfmts --help' or 'update-binfmts --usage' for more information. jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ exit logout
C:\Users\KayZn>wsl --shutdown
C:\Users\KayZn>wsl jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ cmd.exe -bash: /mnt/c/Windows/system32/cmd.exe: cannot execute binary file: Exec format error jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$
Didn't work, i'll try on another distro i guess
jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ cmd.exe -bash: /mnt/c/Windows/system32/cmd.exe: cannot execute binary file: Exec format error jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ vim /etc/wsl.conf jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ sudo vim /etc/wsl.conf [sudo] password for jt: jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ exit logout
C:\Users\KayZn>wsl --shutdown
C:\Users\KayZn>wsl jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ cmd.exe Microsoft Windows [version 10.0.19045.3570] (c) Microsoft Corporation. Tous droits réservés.
C:\Users\KayZn>exit
I get this when i comment the systemd boot part in /etc/wsl.conf
Okay, is exegol working now ?
No because exegol needs the systemd, so if I use the default I have cmd but not exegol but with [boot] systemd=true then i don't have access to cmd.exe I guess you can close the issue because I wont do further debbuging
Sorry to hear that. You are the first with this problem.. maybe a recent upgrade. We will try to reproduce, which distro did you use on WSL2 ?
If you need a workaround, you can install the exegol wrapper in your Windows directly using powershell for example. You just need to have python3 and pip install on windows to run in powershell the pip install command: https://exegol.readthedocs.io/en/latest/getting-started/install.html#installation-of-exegol
C:\Users\KayZn>wsl --list Distributions du Sous-système Windows pour Linux : Debian (par défaut) docker-desktop docker-desktop-data
C:\Users\KayZn>wsl jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" jt@DESKTOP-EUI8PI0:/mnt/c/Users/KayZn$ exit logout
C:\Users\KayZn>wsl --version Version WSL : 1.2.5.0 Version du noyau : 5.15.90.1 Version WSLg : 1.0.51 Version MSRDC : 1.2.3770 Version direct3D : 1.608.2-61064218 Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Version de Windows : 10.0.19045.3570
C:\Users\KayZn>wsl -l -v NAME STATE VERSION
C:\Users\KayZn> I can export the image if you want to investigate further
Hello @KayZ-Safeit your problem should be fixed now on the lastest dev version of the wrapper.
If you want to test now, you can do a source installed (new pip version not released yet).
Describe the bug
Host OS
Windows 10 and before
Configuration of the concerned container
No response
Execution logs in debug mode
Exception
No response
Anything else?
No response