Expected behavior
vpnkit should start. It is working properly on 4.18.0
Actual behavior
vpnkit fails and some host network functionality no longer functions (ex: reaching the AWS EC2 metadata endpoint from within a container).
I have been able to reproduce this across multiple users and machines (work and personal). Has been tested on x86, M1, and M2 machines.
Information
- macOS Version: 13.3.1
- Intel chip or Apple chip: Intel/M1/M2
- Docker Desktop Version: 4.19.0
Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
...
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* com.docker.vpnkit is not running
...
[FAIL] DD0009: is the vpnkit API responding? dial unix vpnkit.diag.sock: connect: connection refused
...
1 : The test: are the backend processes running?
Failed with: 1 error occurred:
* com.docker.vpnkit is not running
Steps to reproduce the behavior
No specific steps. On every machine so far it occurs 100% of the time with 4.19.0, across docker and computer restarts. If I can provide any additional information, please let me know.
Expected behavior
vpnkit should start. It is working properly on 4.18.0
Actual behavior
vpnkit fails and some host network functionality no longer functions (ex: reaching the AWS EC2 metadata endpoint from within a container).
I have been able to reproduce this across multiple users and machines (work and personal). Has been tested on x86, M1, and M2 machines.
Information
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose checkSteps to reproduce the behavior
No specific steps. On every machine so far it occurs 100% of the time with 4.19.0, across docker and computer restarts. If I can provide any additional information, please let me know.