-
Notifications
You must be signed in to change notification settings - Fork 288
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
engine linux/wsl failed to run #14445
Comments
@bsousaa I suddenly noticed the same error. WSL itself is running without any issues running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-29T08:43:06.983715802Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdc,/dev/sde" DiagnosticsId: C8D509D5-368B-4030-BF82-B30E23F69E96/20241129084428 |
@toanphan1302 did you find a way to resolve the issue? |
Not yet. |
I had the same issue. Reset to factory defaults didn't solve it. |
Im used this solution: https://desktop-stage.docker.com/win/main/amd64/176956/Docker%20Desktop%20Installer.exe Reinstal dd by new dev build and its worked. |
Hey all, Thank you for reporting the issue and for your patience. As noted above, this is a duplicate of #14453. As discussed in that ticket, you can install the development build that is shared above. The same fix will be released in the upcoming 4.37 release. I am closing this issue now because of duplication. Please, keep reporting any other problem or feedback you may still have about this issue on #14453. |
Description
running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-25T08:14:09.482596405Z][wsl-bootstrap][F] preparing block device /dev/sdd: detecting file system: detecting fs type: exec: "blkid": executable file not found in $PATH"
Reproduce
Expected behavior
No response
docker version
docker info
Diagnostics ID
680879A2-1507-4D8B-B7F3-FF860FC8D8DC/20241125081519
Additional Info
No response
The text was updated successfully, but these errors were encountered: