self-diagnose tool doesn't work at all on either arm64 or amd64

[rfay]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Expected behavior

Self-diagnose tool should do something useful

Actual behavior

testbot@rfay-m1-air ~ % /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] 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?
[FAIL] DD0016: is the LinuxKit VM running? vm is not running: vm has not started
[PASS] DD0001: is the application running?
[PASS] DD0018: does the host support virtualization?
[FAIL] DD0017: can a VM be started? vm has not started: vm has not started
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy 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] DD0019: is the com.docker.vmnetd process responding?
[PASS] DD0033: does the host have Internet access?

Please investigate the following 1 issue:

1 : The test: can a VM be started?
    Failed with: vm has not started: vm has not started

The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

Information

• macOS Version: 12.2.1
• Intel chip or Apple chip: Apple and Intel (tested both places, same result)
• Docker Desktop Version: 4.6.0

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

See above. It doesn't seem to work at all. Tested on both arm64 and amd64

Steps to reproduce the behavior

1. ...
2. ...

[gmcquistin]

I had a similar issue with 4.6. I reinstalled 4.5, used the 4.5 uninstaller (under diagnostics) and then reinstalled 4.6 fresh

[mat007]

Thanks for pointing this out, we will be fixing this shortly in a Docker Desktop 4.6.1 release.

[mat007]

Docker Desktop 4.6.1 has been released, with a fix. Thanks!

[docker-robott]

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