Supported recovery of Docker Desktop 4.96.0.243774 per-user registration with existing WSL disks under a packaged-app LocalCache
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- docker
- 领域
- desktop-dev
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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:
- 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?
- 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?
- 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?
- Must installation/startup occur from an unpackaged interactive Windows context? How should per-package registry/file visibility be diagnosed without altering the original data?
- 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?
- 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
- 主要语言
- 没有语言数据
- 星标
- 53
- 派生
- 24
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
docker/desktop-feedback 的其他 Issue
-
Codex sandbox template seeds MCP gateway config with keys Codex does not recognize (type, headers)未关闭platform/macos
难度 1/5 1-3 小时 新手友好度 82/100
docker/desktop-feedback#721 ·
-
kind/enhancement
难度 2/5 1-3 小时 新手友好度 68/100
docker/desktop-feedback#259 ·
-
kind/bug platform/windows
难度 4/5 3-5 天 新手友好度 45/100
docker/desktop-feedback#862 ·
-
kind/bug platform/windows
难度 5/5 一周以上 新手友好度 45/100
docker/desktop-feedback#861 ·
-
kind/bug platform/macos
难度 4/5 3-5 天 新手友好度 48/100
docker/desktop-feedback#860 ·
查看 docker/desktop-feedback 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 70/100
milind-soni/OpenMausBot#6495 ·
维护者通常 1 天内回复
-
bug triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 63/100
telegramdesktop/tdesktop#31653 ·
维护者通常 1 天内回复
-
enhancement ui/ux
难度 2/5 1-3 小时 新手友好度 68/100
jbigler/railswitch#243 ·
维护者通常 1 天内回复
-
技能库不能筛选仅可更新的未关闭bug
难度 2/5 1-3 小时 新手友好度 63/100
xingkongliang/skills-manager#678 ·
维护者通常 1 天内回复