OS: Windows 10 Pro - BuildNumber: 19045
I tried to update Docker Desktop 4.39.0 (from 4.38.0) using the interface, but Docker disappeared along with the distribution in the WSL.
Effects:
- Windows Subsystem for Linux doesn’t have any distributions installed. But it did.
- Docker Desktop disappeared (menu and startup)
- Docker disappeared from the cmd
- Relevant log in this case (C:\ProgramData\DockerDesktop\install-log-admin.txt):
[2025-03-18T12:50:11.354689700Z][InstallWorkflow-PatchStep][I] Running C:\Program Files\Docker\Docker\courgette64.exe -applybsdiff -nologfile "C:\Program Files\Docker\Docker\resources\Docker desktop.exe" "C:\Users\<obfuscated>\AppData\Local\Temp\DockerDesktop\m5wn4jn10qw\resources\Docker desktop.exe.bsdiff" "C:\Program Files\Docker\Docker\resources\Docker desktop.exe_"
[2025-03-18T12:50:11.546924900Z][InstallWorkflow-PatchStep][I] Running C:\Program Files\Docker\Docker\courgette64.exe -applybsdiff -nologfile "C:\Program Files\Docker\Docker\resources\docker-desktop.iso" "C:\Users\<obfuscated>\AppData\Local\Temp\DockerDesktop\m5wn4jn10qw\resources\docker-desktop.iso.bsdiff" "C:\Program Files\Docker\Docker\resources\docker-desktop.iso_"
[2025-03-18T12:50:21.169816900Z][InstallWorkflow][E] Patching failed Failed to apply delta update
[2025-03-18T12:50:21.169816900Z][InstallWorkflow][E] Installation failed Docker.Installer.DeltaUpdateFailedException: Failed to apply delta update ---> System.Exception: File patching failed
en Docker.Installer.PatchStep.<PatchAsync>d__37.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en Docker.Installer.PatchStep.<DoAsync>d__35.MoveNext()
--- Fin del seguimiento de la pila de la excepción interna ---
en Docker.Installer.PatchStep.<DoAsync>d__35.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.Installer.InstallWorkflow.<DoHandleD4WPackageAsync>d__30.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en Docker.Installer.InstallWorkflow.<DoHandleD4WPackageAsync>d__30.MoveNext()
--- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
en Docker.Installer.InstallWorkflow.<DoProcessAsync>d__23.MoveNext()
[2025-03-18T12:50:21.171741100Z][InstallWorkflow][I] Rollbacking component Docker.Installer.UnpackArtifactsStep
[2025-03-18T12:50:21.177366500Z][FileSystem][I] Deleting C:\Users\<obfuscated>\AppData\Local\Temp\DockerDesktop\m5wn4jn10qw
[2025-03-18T12:50:21.256351300Z][FileSystem][I] Deleted C:\Users\<obfuscated>\AppData\Local\Temp\DockerDesktop\m5wn4jn10qw successfully
[2025-03-18T12:50:21.256351300Z][InstallWorkflow][I] Rollbacking component Docker.Installer.ExtractManifestStep
[2025-03-18T12:50:21.256861600Z][InstallWorkflow][I] Rollbacking component Docker.Installer.DownloadStep
The only thing I consider unusual that could have possibly caused the problem is that earlier that day I tried unsuccessfully to compact the VHDX disk “wsl\disk\docker_data.vhdx” because it was 250GB by the “binwalk” tool, filled the disk with repetitive garbage (The tool extracted more than 100GB from a 780MB file, I guess I invoked the command with some error). To try compacting, I used the following methods:
- Optimize-VHD -Path "C:\Users\<user>\AppData\Local\Docker\wsl\disk\docker_data.vhdx" -Mode Full
-
diskpart + => select vdisk file=“” + => compact vdisk
-
fstrim -av(inside wsl)
None of the above methods reduced the disk size of docker_data.vhdx (viewed from Windows after refreshing F5). However, they all ran and showed no problems. The junk files generated by “binwalk” had been removed before. I’m going to start using disk limits on the containers to prevent this from happening again.
I’m currently trying to install the previous version 4.38.0.
