An unexpected error occurred

[thany]

Description

Just trying to start Docker as always, which has always worked. The only thing that changed, was it updated to 4.37 (up from 4.36).

In the Hyper-V manager, I'm not seeing the VM, which could very well be the cause of the error. Should I see it there? If so, why was it deleted? Or better yet, why is it not reinstated automatically?

Reproduce

1. Have Docker Desktop 4.36
2. Have Windows dockers enabled
3. Update to 4.37

Expected behavior

Should just work as it always has

docker version

Client:
 Version:           27.4.0
 API version:       1.47
 Go version:        go1.22.10
 Git commit:        bde2b89
 Built:             Sat Dec  7 10:40:21 2024
 OS/Arch:           windows/amd64
 Context:           desktop-windows
request returned Internal Server Error for API route and version http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/v1.47/version, check if the server supports the requested API version

docker info

Client:
 Version:    27.4.0
 Context:    desktop-windows
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.5.1
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.19.2-desktop.1
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.31.0-desktop.2
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     C:\Users\martijn\.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:\Users\martijn\.docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.1
    Path:     C:\Users\martijn\.docker\cli-plugins\docker-scout.exe

Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/v1.47/info": open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

56895DE2-B12F-40EE-B8FE-062E209765D2/20241217092952

Additional Info

It's important to emphasise I'm running Windows dockers (or trying to). Previous similar problems all referred to WSL, which is obviously not relevant to this issue, even though, yes, I do have WSL running as well, just not active for the docker engine.

[thany]

Maybe it's worth noting that if I switch to linux containers, all is well. Everything works. But, that of course isn't useful to me, because I need windows containers. Switch back to windows containers brings me back to the original problem again. The same error, still nothing in the Hyper-V manager (should there be anything in the first place??).

Have another diagnostics ID, just in case something changed after my fiddling around with the error:
CDAAB5BF-3140-4B8D-92B0-7BF2F42B5FA4/20250102094515

[thany]

One more update on something I tried:

1. Uninstall Docker completely
2. Reinstall Docker from a fresh download from the main website (which is luckily behind on version 4.36.0)
3. Observe how everything is working just fine
4. Update to 4.37.1 from within the application
5. Boom, the same problem is back again

So I do think 4.37.x breaks windows dockers in some generic/unexpected way. Perhaps 4.37 is a test version or similar, hence why it's not on the website, but then I wonder if the application isn't supposed to skip that version in its update feature.