Getting message about WSL not being able to find docker.exe when in docker desktop and starting and stopping a compose stack

[dkwgit]

It does not seem to be causing any problems and everything appears to be working, but when I look at a compose stack (which I started from the WSL side) and I start or stop the stack, I get a message seemingly related to WSL not being able to find docker.exe via a Windows path.

Example:

"<3>WSL (71600) ERROR: CreateProcessCommon:559: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory"

Here is a screenshot:

I'm in Windows 11 Docker Desktop 4.38.0 WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65

[Gazmataz]

Same

[Eric-Montgomery]

I am having the same issue. Windows 11 WSL version: 2.4.11.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65

[ahanley]

I'm getting the same issue as well.

[infstellar]

same issue but it seems doesn't matter to my application.

[mpeyrac]

same

[mdkitzman]

Same issue here on Docker Desktop 4.38.0 Windows 11 WSL version: 2.3.24.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.3323

[mdkitzman]

I contacted customer support for this issue (we have a business account through my work) and was told to try and reinstall Docker Desktop.

I tried this and it did not work for me. They also told me that I can safely ignore this.

My takeaway is that this will likely not be a priority for them to look into

[mpeyrac]

@mdkitzman How can it be ignored though, my containers won't start with this error?

[bsousaa]

This will be fixed with 4.39

[eueliseeu]

I'm facing the same problem even after updating to 3.39, the issue persists.

"<3>WSL (71600) ERROR: CreateProcessCommon:559: execvpe(C:\Program Files\Docker\Docker\resources\bin\docker.exe) failed: No such file or directory""

[avi-arora]

Same error