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

Abierto
#856 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
docker
Área
desktop-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Sin datos de lenguaje
Estrellas
53
Forks
24
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de docker/desktop-feedback

Todos los issues de docker/desktop-feedback

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.