Repository navigation
Docker desktop 4.36.0 fails to start with "more than one sd* disk in /sys/block" #14453
Description
Description
Unable to start docker desktop version 4.36.0; I am consistently seeing the following error:
running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-28T16:04:44.799442528Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdb,/dev/sdd"
Reproduce
Start docker desktop
Expected behavior
Docker desktop should start successfully
docker version
Client:
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:42:27 2024
OS/Arch: windows/amd64
Context: desktop-linuxdocker info
Client:
Version: 27.3.1
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.1.0
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.18.0-desktop.2
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.30.3-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.37
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.15
Path: C:\Program Files\Docker\cli-plugins\docker-desktop.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version: v1.15.0
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
ERROR: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/info": context canceled
errors pretty printing infoDiagnostics ID
1AA58D3A-8AF2-493C-AEAF-41A589D2DF25/20241128162112
Additional Info
WSL version info:
wsl --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460
Reacted by UnrealKazu, Kaur Oks, BkCoding, Mathias Lengler, queensjacket, Sudipto Sarkar, Mathew Rumsey, Richard Homewood, Scott Charlesworth, RaynLegends and 16 more
Activity
MarcelBolten commentedon Nov 28, 2024
Hi,
I'm also observing the same error:
running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-28T19:48:55.345483430Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdc,/dev/sde"docker version
docker info
Diagnostics ID
ECCA2C28-89D7-4B8B-93C2-DBB853C4B6E2/20241128194210
Additional Info
WSL version info:
beegotsy commentedon Nov 29, 2024
For those who need to get Docker working; rollbacking to 4.35.1 (release page) works:
You will need to rebuild all images and containers, or at least that's what I did.
For me, the WSL update changed the error from a generic one to
more than one sd* disk in /sys/block with wwid ending by ....This seems a fix to get 4.36.0 working: #14447 (comment)
griesi007 commentedon Nov 29, 2024
same issue for me #14445
rupasix commentedon Nov 29, 2024
I have same issue, screenshot from error:
After that i checked with command "lsblk" if there is sde block and there was none:
lerouxm commentedon Nov 29, 2024
Same issue here with an up to date wsl.
I can confirm that rolling back to previous 3.5.1 fixed the problem for me for now.
dev-mich commentedon Nov 29, 2024
I had the same issue, but completely uninstalling and reinstalling resolved it for me.
bastian-kurz commentedon Nov 29, 2024
I had the same issue. I solved it by going to 'Troubleshoot,' then clicking on 'Clean/Purge Data,' and selecting 'Hyper-V & WSL2.
after that Docker Engine starts again.
andrea-reale commentedon Nov 29, 2024
Hello everyone,
thanks for reporting the problem. Could you please share the output of
wsl --list?From the diagnostics kindly shared by @chris-riddell35 , it looks like WSL2 is in a state where it believes there are two disks with the same identifiers, which makes Docker Desktop boot fail.
Could you please confirm if shutting down WSL after quitting Docker Desktop (
wsl.exe --shutdown) helps fixing the issue or not? (Alternative a Windows restart should also be equivalent)chris-riddell35 commentedon Nov 29, 2024
Hi @andrea-reale ,
I've done several Windows restarts, with the same result each time.
Here's the output of
wsl --list:andrea-reale commentedon Nov 29, 2024
Hey @chris-riddell35 ,
thanks for your quick response and for confirming. I am having a hard time to try and reproduce the issue.
However, I will be shortly sharing a development build of Docker Desktop with a tentative fix.
I'd sincerely appreciate if you could help us by trying it out and confirm if it addresses the problem or not. If it does, I'll try to get it included in the upcoming 4.37 release.
andrea-reale commentedon Nov 29, 2024
@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.
Please, let me know if that helps with the
more than one sd* diskerror discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file ->
Properties->Unblock.thomaswiradikusuma commentedon Nov 29, 2024
I had exactly this error as well, right after upgrading. It disappears after few times open-crash-close-open-crash-close-open :)
Cristy94 commentedon Nov 29, 2024
I have the same issue with 4.36.0, it suddenly stopped working.
44 remaining items
NotVeryAsh commentedon Dec 16, 2024
Running only this command seemed to work for me 😄
vivirox commentedon Dec 22, 2024
Still there for me. Two systems, one was/is experiencing after latest upgrade. The other system, completely fresh Windows install straight to 4.37.1. Windows 11.
Neither Docker Desktop will ever actually start. The service, if on, gets stopped and disabled almost immediately. If 'Automatic' was set, that status gets washed. Never starts though.
WesWedding commentedon Dec 22, 2024
To be clear, you're getting the error shown in the OP?
jlegue commentedon Dec 22, 2024
vivirox commentedon Dec 22, 2024
Yes. Same error. That's what brought me here.
I've tried about every possible 'workaround' or alleged fix possible. No dice.
WesWedding commentedon Dec 22, 2024
vivirox commentedon Dec 23, 2024
wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
docker-desktop
WesWedding commentedon Dec 23, 2024
Not sure what the appropriate way to get attention back into this issue is. A full diagnostic report like the OP generated would probably help significantly, or perhaps there's a process to generate a support request.
ksaber commentedon Dec 27, 2024
Guys, first time using Docker and for almost 2 weeks now i have tried almost every solution. If anyone can help my diagnostic code is "CDF346CC-88C2-4F95-84DF-33986A062672/20241227054541"
edisanch commentedon Jan 30, 2025
I've been using docker for about a month on my windows 11 machine. Usinw WLS2. Currently Docker desktop is V4.37.1, yesterday, it crashed,
running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2025-01-30T10:22:22.849980818Z][wsl-bootstrap][F] exit status 32" I have tried everything in this issues thread, except basically removing my wsl. As I have lots of work there that would take time for me to backup and reproduce.
Anyone has any idea ?
Diagnostics ID. A54CC16C-3CF3-417A-8F05-A436658473EE/20250130101631
WesWedding commentedon Jan 31, 2025
I would recommend finding a way to open a different issue or trying to find a different thread, this one doesn't obviously match the specific issue you are encountering without additional log information.
Consider opening a ticket here: https://hub.docker.com/support/contact/
lamy commentedon Jul 4, 2025
lamy commentedon Jul 4, 2025
lamy/github
Winand commentedon Nov 5, 2025
FINALLY I've managed to fix this issue on 4.36.0 by changing the VHDX disk identifier:
Set-VHD -Path "$env:USERPROFILE\AppData\Local\Docker\wsl\disk\docker_data.vhdx" -ResetDiskIdentifierFirst I checked the ids of /dev/sd* devices via docker-desktop WSL distro without trying to start Docker:
for disk in /sys/block/sd*; do echo -n "$disk: "; cat "$disk/device/wwid" 2>/dev/null; doneThen I checked ID of the Docker's data disk:
Get-VHD -Path "$env:USERPROFILE\AppData\Local\Docker\wsl\disk\docker_data.vhdx"There's already a /dev/sd* device with the same ID as my VHDX file. When I try to start Docker Desktop it tries to add a device with this ID again what leads to a confict.