Repository navigation
Cannot start Docker Compose application after 4.10.0 update #12806
Copy link
Copy link
Closed
Labels
Description
Unable to perform "Run All" on grouped containers created by docker-compose. The docker desktop displays the error:

- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID:
Actual behavior
Error when running all containers via Docker Desktop 'play' button
Expected behavior
Be able to run all containers at once
Information
- Windows Version: Windows 11 Home, Version 21H2 (OS Build: 22000.778)
- Docker Desktop Version: 4.10.0
- WSL2 integrated as I'm running Home Version
- WSL2 Distro Used: Ubuntu 20.04
- Are you running inside a virtualized Windows e.g. on a cloud server or a VM:
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0024: is WSL installed?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* vpnkit.exe is not running
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
Please investigate the following 1 issue:
1 : The test: are the backend processes running?
Failed with: 1 error occurred:
* vpnkit.exe is not running
Not all of the backend processes are running.
Current work around is to do all on WSL2 terminal or the Docker extension on VSCode
Checking the issue: vpnkit.exe seems to be running? but docker wasn't able to detect it?

Reacted by Marco Lackovic and Jorran de Wit
Activity
trungutt commentedon Jul 1, 2022
Hi @andROYdified what's the docker compose version that you're using?
lackovic commentedon Jul 1, 2022
Same problem here on Windows 10 21H1 and Ubuntu 22.04 WSL2.
aljagne commentedon Jul 1, 2022
I do have the same problem everything was working fine before updating to 40.10. and now Docker can't start
StefanScherer commentedon Jul 1, 2022
We have identified the problem and working on a fix. Thanks for reporting!
andROYdified commentedon Jul 1, 2022
Hi @trungutt , not sure if it's still relevant, but I'm using the same version as @lackovic
And thank you too @StefanScherer :) You guys rock!
maxcleme commentedon Jul 5, 2022
This issue has been fixed in latest release, please consider updating to latest version and give us your feedback!
4.10.1 Release notes
andROYdified commentedon Jul 6, 2022
Hi @maxcleme , confirming that the issue was fixed with the latest release.
Thanks a lot!
silenaker commentedon Jul 8, 2022
I upgraded to 4.10.1 but diagnose still report "vpnkit.exe is not running"
docker-robott commentedon Aug 7, 2022
Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked