4.38.0 update docker.exe not found

[Deffz-Finesse]

Description

After updating Docker desktop to 4.38.0, when attempting to look at my containers overall logs I see the error:

<3>WSL (11071 - Relay) ERROR: CreateProcessCommon:640: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory

After checking the docker.exe is present in the correct location, downgrading to 4.37.1 fixes the issue

Reproduce

Update to 4.38.0 from 4.37.1

Expected behavior

No response

docker version

4.38.0

docker info

<3>WSL (11071 - Relay) ERROR: CreateProcessCommon:640: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory

Diagnostics ID

ADDC1AE8-CD4A-47BB-906C-1CE9A37E3DC7/20250207003332

Additional Info

No response

[colinwoolmer40]

I have the same issue. Downgrading will be painful for me. Lots of images to backup

[wwh1004]

The same problem.

[tooruu]

Same here.

[alvin-sunco]

Same:
<3>WSL (1122) ERROR: CreateProcessCommon:559: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory.
I ran a log collecting script I found in another post:

WslLogs-2025-02-11_10-53-20.zip

[edysonMO]

I run docker in WSL2, and use ubuntu as another WSL to start my containers. I am experiencing the same issue.
<3>WSL (7480 - Relay) ERROR: CreateProcessCommon:640: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory
Commenting in hopes of someone posting a fix for the issue. My individual container logs are still working but it would be nice to be able to see my overall logs again without having to click container to container.

[Deffz-Finesse]

I run docker in WSL2, and use ubuntu as another WSL to start my containers. I am experiencing the same issue. <3>WSL (7480 - Relay) ERROR: CreateProcessCommon:640: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory Commenting in hopes of someone posting a fix for the issue. My individual container logs are still working but it would be nice to be able to see my overall logs again without having to click container to container.

What I'm done was delete Docker Desktop and reinstall, but don't update and its working fine again

[creativestate]

Perform a simple in-place downgrade.

X:\Downloads>"Docker Desktop Installer 4.37.1.exe" install --disable-version-check

Link to the previous docker versions: https://docs.docker.com/desktop/release-notes/#4371
And for the lazy ones: https://desktop.docker.com/win/main/amd64/178610/Docker%20Desktop%20Installer.exe

4.38.0 causes specific containers in my case to not work correctly along with the error mentioned above.

Downgrading to 4.37.1 fixes the issues with the odd container behavior and errors within docker.

This is the third time within a year where newer versions have broken things, so a downgrade has always been necessary (on Windows only), I have not had any issues on Docker Desktop for Mac.

Keep the downgrade command handy for instances like this.

[Ali-Fawzi]

Rolling back to the version 4.37.1 was the solution make sure to back up all your images in case you need them and load them again after installing the older version

[edysonMO]

Rolling back to the version 4.37.1 was the solution make sure to back up all your images in case you need them and load them again after installing the older version

Back up to be safe, but I did the in-place downgrade and all of my containers, images, and volumes persisted.

• Download the desired version you want to downgrade to
• Open a powershell in that same location (may have to open powershell as admin)
• Run ./"Docker Desktop Installer.exe" install --disable-version-check

[Deffz-Finesse]

Perform a simple in-place downgrade.

X:\Downloads>"Docker Desktop Installer 4.37.1.exe" install --disable-version-check

Link to the previous docker versions: https://docs.docker.com/desktop/release-notes/#4371 And for the lazy ones: https://desktop.docker.com/win/main/amd64/178610/Docker%20Desktop%20Installer.exe

4.38.0 causes specific containers in my case to not work correctly along with the error mentioned above.

Downgrading to 4.37.1 fixes the issues with the odd container behavior and errors within docker.

This is the third time within a year where newer versions have broken things, so a downgrade has always been necessary (on Windows only), I have not had any issues on Docker Desktop for Mac.

Keep the downgrade command handy for instances like this.

Yh, I always try to hold off a Docker Desktop update as long possible