You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 4.39, when Docker Desktop tries to start, it fails immediately.
The first time I got this error: running engine: waiting for the VM setup to be ready: starting windows containers: status code not OK but 500: Unhandled exception: Time out has expired and the operation has not been completed.
On all subsequent starts, I get this error: running engine: waiting for the Docker API: engine windows failed to run: getting docker info: error during connect: Get "http://%5C%5C.%5Cpipe%5Cdocker_engine_windows/v1.48/info": open \\.\pipe\docker_engine_windows: The system cannot find the file specified.
Reproduce
Start Docker Desktop
Expected behavior
No response
docker version
Client:
Version: 28.0.1
API version: 1.48
Go version: go1.23.6
Git commit: 068a01e
Built: Wed Feb 26 10:41:52 2025
OS/Arch: windows/amd64
Context: desktop-windows
error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/v1.48/version": open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
docker info
Client:
Version: 28.0.1
Context: desktop-windows
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v0.9.4
Path: C:\Program Files\Docker\cli-plugins\docker-ai.exe
buildx: Docker Buildx (Docker Inc.)
Version: v0.21.1-desktop.2
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.33.1-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.38
Path: C:\Program Files\Docker\cli-plugins\docker-debug.exe
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.5
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.16.3
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/v1.48/info": open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
errors pretty printing info
Description
After upgrading to 4.39, when Docker Desktop tries to start, it fails immediately.
The first time I got this error:
running engine: waiting for the VM setup to be ready: starting windows containers: status code not OK but 500: Unhandled exception: Time out has expired and the operation has not been completed.
On all subsequent starts, I get this error:
running engine: waiting for the Docker API: engine windows failed to run: getting docker info: error during connect: Get "http://%5C%5C.%5Cpipe%5Cdocker_engine_windows/v1.48/info": open \\.\pipe\docker_engine_windows: The system cannot find the file specified.
Reproduce
Expected behavior
No response
docker version
Client: Version: 28.0.1 API version: 1.48 Go version: go1.23.6 Git commit: 068a01e Built: Wed Feb 26 10:41:52 2025 OS/Arch: windows/amd64 Context: desktop-windows error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/v1.48/version": open //./pipe/dockerDesktopWindowsEngine: The system cannot find the file specified.
docker info
Diagnostics ID
16A537D7-399D-4316-AD25-E79003CE7CE2/20250307080138
Additional Info
No response
The text was updated successfully, but these errors were encountered: