search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.87k stars 290 forks source link

Docker desktop 4.36.0 fails to start with "more than one sd* disk in /sys/block" #14453

Open chris-riddell35 opened 3 days ago

chris-riddell35 commented 3 days ago

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-linux

docker 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 info

Diagnostics 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
MarcelBolten commented 3 days ago

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

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-linux
error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/version": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.

docker 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: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/info": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

ECCA2C28-89D7-4B8B-93C2-DBB853C4B6E2/20241128194210

Additional Info

WSL version info:

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
beegotsy commented 2 days ago

For those who need to get Docker working; rollbacking to 4.35.1 (release page) works:

# install pending WSL updates with
wsl.exe --update
# install the previous version of Docker for Windows with:
.\<installer path>.exe install --disable-version-check

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: https://github.com/docker/for-win/issues/14447#issuecomment-2504140336

griesi007 commented 2 days ago

same issue for me https://github.com/docker/for-win/issues/14445

rupasix commented 2 days ago

I have same issue, screenshot from error:

Image

After that i checked with command "lsblk" if there is sde block and there was none: Image

lerouxm commented 2 days ago

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 commented 2 days ago

I had the same issue, but completely uninstalling and reinstalling resolved it for me.

bastian-kurz commented 2 days ago

I had the same issue. I solved it by going to 'Troubleshoot,' then clicking on 'Clean/Purge Data,' and selecting 'Hyper-V & WSL2.

Image

after that Docker Engine starts again.

andrea-reale commented 2 days ago

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 commented 2 days ago

Hi @andrea-reale ,

I've done several Windows restarts, with the same result each time.

Here's the output of wsl --list:

wsl --list -v
  NAME              STATE           VERSION
* Ubuntu-20.04      Running         2
  Ubuntu            Stopped         1
  Ubuntu-24.04      Stopped         2
  docker-desktop    Stopped         2
andrea-reale commented 2 days ago

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 commented 2 days ago

@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* disk error 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 commented 2 days ago

I had exactly this error as well, right after upgrading. It disappears after few times open-crash-close-open-crash-close-open :)

Cristy94 commented 2 days ago

I have the same issue with 4.36.0, it suddenly stopped working.

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-29T15:17:21.165474510Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdc,/dev/sdd"
wsl --list
Windows Subsystem for Linux Distributions:
docker-desktop (Default)
Cristy94 commented 2 days ago

I had the same issue. I solved it by going to 'Troubleshoot,' then clicking on 'Clean/Purge Data,' and selecting 'Hyper-V & WSL2.

Image

after that Docker Engine starts again.

Where did you find "Troubleshoot"?

Nevermind, it's here:

Image

EDIT:

Purging the data works (note that you will lose all containers).

salvorapi commented 2 days ago

@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* disk error 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.

it work 👍

chris-riddell35 commented 2 days ago

@andrea-reale after installing and restarting, docker desktop is up and running but something is wrong with the wsl2 integration. I see this error message:

Image

Diagnostics ID: 1AA58D3A-8AF2-493C-AEAF-41A589D2DF25/20241129155916

If I run docker from powershell, it's working. I typically use wsl2 and I have all my configurations there so this is still inconvenient, but appears to be workable. Let me know if I can gather more information about the new error.

chris-riddell35 commented 2 days ago

@andrea-reale I disabled the WSL integration, re-enabled and restarted Windows and this seems to be working now. I lost all my images when I did that, but I think the system is ok now.

I had also had two wsl2 distros active there, and I disabled one of them. I guess that may have helped fix this issue.

Image

andrea-reale commented 2 days ago

Hey @chris-riddell35 , thanks for reporting back your experience.

Glad to hear that the dev build fixed at least the startup issue. And I am sorry about the troubles with the Ubuntu integration. It looks like the previous integration moved to an unhealthy state after the upgrade: glad that disabling it and enabling it again mitigated the problem.

I'll look more into the diagnostics you provided to understand more about why the integration issue started to begin with.

SparkInChief commented 2 days ago

@andrea-reale — The dev build resolved the issue for me as well (same error message immediately after upgrading to 4.36.0).

I did not have to reboot (or purge anything), but I did lose all locally cached images and had to rebuild all images and restart containers.

Here's output of wsl --version in case it helps determine what systems the dev build works for (and why it doesn't work on others):

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.4541
neonima1995 commented 1 day ago

Removing Ubuntu from Windows helped me.ImageImage

theswissguy commented 6 hours ago

'Troubleshoot,' then clicking on 'Clean/Purge Data,' helped in my case. Docker Desktop starts, but in won't let my sign in. I'm been redirected to https://app.docker.com/auth/ and back to Docker Desktop, but all I get is

Image