Docker Desktop 4.47 service disk panicked

[D4V3M0NK]

Description

Ubuntu 25.04 system has been running Docker Desktop for a couple of years, no major issues. Today I upgraded to 4.47 and received the following unexpected error:

service disk panicked: map[], stack: goroutine 84 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:26 +0x5e
github.com/docker/pinata/common/pkg/services.runServers.func1.1()
	github.com/docker/pinata/common/pkg/services/start.go:121 +0xa5
panic({0x26089c0?, 0xc000734a08?})
	runtime/panic.go:783 +0x132
github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk.extend({0x2787fe0, 0xc0005bec30}, {0xc0001d8978, 0x8})
	github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk/extend.go:57 +0x80c
github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk.mountReadWriteDisk({0x2787fe0, 0xc0005bec30}, {0x1cda47a, 0x8})
	github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk/mount.go:41 +0x126
github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk.Mount({0x2787fe0, 0xc0005bec30}, 0x0)
	github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/disk/mount.go:16 +0x6a
github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base.(*baseServices).startDisk-fm.(*baseServices).startDisk.func1({0x2787fe0, 0xc0005bec30})
	github.com/docker/pinata/linuxkit/pkg/init/cmd/init/base/services.go:194 +0x2a
github.com/docker/pinata/common/pkg/services.runServers.func1()
	github.com/docker/pinata/common/pkg/services/start.go:135 +0x15f
golang.org/x/sync/errgroup.(*Group).Go.func1()
	golang.org/x/sync@v0.17.0/errgroup/errgroup.go:93 +0x50
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 31
	golang.org/x/sync@v0.17.0/errgroup/errgroup.go:78 +0x95

When I select Gather Diagnostics the system appears to be gathering, but I kinda gave up after 20 minutes of it doing so.

Reproduce

Reverting to 4.43 isn't an issue and works perfectly. Using the Desktop app to download 4.47 reproduces the error.

Expected behavior

Upgrade over prior versions have been uneventful up until now

docker version

lient: Docker Engine - Community
 Version:           28.3.3
 API version:       1.51
 Go version:        go1.24.5
 Git commit:        980b856
 Built:             Fri Jul 25 11:33:50 2025
 OS/Arch:           linux/amd64
 Context:           desktop-linux
Cannot connect to the Docker daemon at unix:///home/dave/.docker/desktop/docker.sock. Is the docker daemon running?

docker info

Client: Docker Engine - Community
 Version:    28.3.3
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Docker AI Agent - Ask Gordon (Docker Inc.)
    Version:  v1.9.11
    Path:     /home/dave/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.28.0-desktop.1
    Path:     /home/dave/.docker/cli-plugins/docker-buildx
  cloud: Docker Cloud (Docker Inc.)
    Version:  v0.4.29
    Path:     /home/dave/.docker/cli-plugins/docker-cloud
  compose: Docker Compose (Docker Inc.)
    Version:  v2.39.4-desktop.1
    Path:     /home/dave/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.42
    Path:     /home/dave/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Docker Inc.)
    Version:  v0.2.0
    Path:     /home/dave/.docker/cli-plugins/docker-desktop
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.31
    Path:     /home/dave/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     /home/dave/.docker/cli-plugins/docker-init
  mcp: Docker MCP Plugin (Docker Inc.)
    Version:  v0.21.0
    Path:     /home/dave/.docker/cli-plugins/docker-mcp
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /home/dave/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.18.3
    Path:     /home/dave/.docker/cli-plugins/docker-scout

Server:
Cannot connect to the Docker daemon at unix:///home/dave/.docker/desktop/docker.sock. Is the docker daemon running?

Diagnostics ID

eeea7e2e-7

Additional Info

I ran /opt/docker-desktop/bin/com.docker.diagnose gather - upload and the last few lines are as follows (understanding that the socket isn't running because Docker Desktop can't start):

[2025-10-06T23:03:22.599773857Z][com.docker.diagnose] Gathering: <HOME>/.docker/cloud/logs/diagnostic.json
[2025-10-06T23:03:22.600231168Z][com.docker.diagnose] Gathering cloud (External) took 608.232551ms
[2025-10-06T23:03:23.111719338Z][com.docker.diagnose.ipc] (eeea7e2e-4) 14626138-DiagkitPKG C->S Virtualization GET /ping
[2025-10-06T23:03:23.111985586Z][com.docker.diagnose.ipc][W] (eeea7e2e-4) 14626138-DiagkitPKG C<-S ConnectionClosed GET /ping (275.962µs): Get "http://ipc/ping": dial unix <HOME>/.docker/desktop/virtualization.sock: connect: no such file or directory
[2025-10-06T23:03:24.112073861Z][com.docker.diagnose.ipc] (eeea7e2e-5) 14626138-DiagkitPKG C->S Virtualization GET /ping
[2025-10-06T23:03:24.112328973Z][com.docker.diagnose.ipc][W] (eeea7e2e-5) 14626138-DiagkitPKG C<-S ConnectionClosed GET /ping (261.011µs): Get "http://ipc/ping": dial unix <HOME>/.docker/desktop/virtualization.sock: connect: no such file or directory
[2025-10-06T23:03:25.112464104Z][com.docker.diagnose.ipc] (eeea7e2e-6) 14626138-DiagkitPKG C->S Virtualization GET /ping
[2025-10-06T23:03:25.112735682Z][com.docker.diagnose.ipc][W] (eeea7e2e-6) 14626138-DiagkitPKG C<-S ConnectionClosed GET /ping (275.295µs): Get "http://ipc/ping": dial unix <HOME>/.docker/desktop/virtualization.sock: connect: no such file or directory
[2025-10-06T23:03:26.112855736Z][com.docker.diagnose.ipc] (eeea7e2e-7) 14626138-DiagkitPKG C->S Virtualization GET /ping
[2025-10-06T23:03:26.113119141Z][com.docker.diagnose.ipc][W] (eeea7e2e-7) 14626138-DiagkitPKG C<-S ConnectionClosed GET /ping (269.777µs): Get "http://ipc/ping": dial unix <HOME>/.docker/desktop/virtualization.sock: connect: no such file or directory
[2025-10-06T23:03:27.113578860Z][com.docker.diagnose] Gathering VirtualizationAPIGatherer took 7.003643256s
[2025-10-06T23:03:27.113633580Z][com.docker.diagnose] All 90 gatherers finished in 7.003967527s


Diagnostics Bundle: -.zip

As you can see, there was no "diagnostic ID" present, so I've used "eeea7e2e-7" which I assume is a thread ID?