Supported recovery of Docker Desktop 4.96.0.243774 per-user registration with existing WSL disks under a packaged-app LocalCache

Đang mở
#856 1 bình luận 0 reaction 0 người được giao Xem trên GitHub

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
8/100
Loại issue
Lỗi
Độ rõ ràng
Cần làm rõ
Mức độ hoạt động
Sôi nổi
Công nghệ
docker
Lĩnh vực
desktop-dev

Hướng nghiên cứu

This is a support request, not a scoped code change: it asks Docker maintainers for a version-specific recovery procedure for a per-user Windows install whose SOFTWARE\Docker Inc.\Docker Desktop and Uninstall registration keys are missing while the WSL disks live under a packaged-app LocalCache path. Whoever triages it should first read Docker Desktop's Windows install/WSL documentation on --wsl-default-data-root and per-user install --user repair, then compare that documented behaviour against the reported launcher error "getting backend binary path: cannot find registry key". Done means answering the six numbered questions and stating which registry keys, WSL registrations and VHDX paths a supported repair touches plus its rollback. Nothing here names a file in the repository, so no code path can be located from the issue alone.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

kind/bug platform/windows
Bug report

Hello Docker maintainers,

We request a supported recovery procedure before making any installation or registry changes.

Environment and confirmed observations:

  • Windows 11 Home x64; Docker Desktop 4.96.0.243774, per-user EXE installation, WSL2.
  • Normal launcher: getting backend binary path: cannot find registry key "SOFTWARE\Docker Inc.\Docker Desktop": The system cannot find the file specified.
  • The launcher, integrated installer and backend executable exist at %USERPROFILE%\AppData\Local\Programs\DockerDesktop and have valid Docker Inc. signatures.
  • An earlier successful launch recognized the historical local synthetic containers and volumes. The per-user uninstall registration had previously been documented as present.
  • Currently both SOFTWARE\Docker Inc.\Docker Desktop and SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Docker Desktop are not found in HKCU/HKLM 32/64-bit reads. The user independently confirmed the HKCU uninstall key is not found in both views from an ordinary desktop command prompt.
  • Effective existing disks are under %USERPROFILE%\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Docker\wsl\disk\docker_data.vhdx and ...\wsl\main\ext4.vhdx. The existing docker-desktop WSL2 registration points its BasePath at the latter main directory.
  • Existing configuration is under the same package's LocalCache\Roaming\Docker. Standard AppData Docker paths are not visible in current diagnostic reads. We have not established whether packaged-context virtualization caused the issue.
  • Docker is stopped. Cold copies of both current VHDX files were created with exclusive read access and matching source-before/source-after/copy SHA256. Historical backups are also preserved; restore has not been tested.
  • The full official 4.96.0.243774 package was downloaded, not run: 650,507,696 bytes, valid Docker Inc. signature, SHA256 3f75d46a07ff7c7adcc42e55b2bab862e25a459351723ac2633de9ad22a5b4b6, matching the official checksum.

Please clarify:

  1. Is running this exact full installer with install --user over the existing installation a supported repair when its uninstall registration is missing? Could it regard the installation as new?
  2. How can the existing docker-desktop distribution and docker_data.vhdx be retained at these effective LocalCache locations without creating a different empty data store?
  3. Does --wsl-default-data-root adopt both existing disks or only set a default for newly created storage? Which exact configuration controls adoption for this build?
  4. Must installation/startup occur from an unpackaged interactive Windows context? How should per-package registry/file visibility be diagnosed without altering the original data?
  5. Can the installer start Docker/WSL or perform technical data migrations before we verify the resulting references and paths? Is there a supported way to defer that start?
  6. Which files, registry references and WSL components would your proposed procedure modify, and what is the supported rollback without deleting or overwriting existing VHDX files?

We will not manually invent registry values, unregister WSL, uninstall/reset Docker or overwrite disks. Please provide version-specific steps or a confirmed fixed build and its preservation requirements.

No credentials, business data, full configuration files or diagnostic bundles are attached. We can provide minimal redacted technical information if needed.

Thank you.

Platform

Windows

Version information
Windows 11 Home x64; Docker Desktop 4.96.0.243774, per-user EXE installation, WSL2.
Diagnostics ID

No response

Ngôn ngữ chính
Không có dữ liệu ngôn ngữ
Star
53
Fork
24
Chỉ số merge pull request
Không có pull request nào được merge trong 30 ngày

Chuẩn bị môi trường

Dự án này không cung cấp dev container, Dockerfile hay hướng dẫn đóng góp, nên bạn cần tự thiết lập môi trường: hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của docker/desktop-feedback

Tất cả issue của docker/desktop-feedback

Issue tương tự

Thêm issue về Desktop Dev

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.