Docker 4.14.0 stops running on MacOS Ventura 13.0.1

makotore commented 2 years ago

After upgrading Docker Desktop to version 4.14.0 and MacOS to 13.0.1 docker stops running after a while. Trying to restart docker fails with the following; Fatal Error supervising tasks: tais com.docker.vpnkit with pid: XXXX failed failed to run backend process

Starting Docker again manually works but it stops running after an hour or so.

[x] I have tried with the latest version of Docker Desktop
[x] I have tried disabling enabled experimental features
[x] I have uploaded Diagnostics
Diagnostics ID: 2BF3916E-9D6D-4528-8514-05C280FC0CE8/20221112031526

Expected behavior

Docker Desktop is expected to continue running without stopping

Actual behavior

Docker stops running after running for a while

Information

This happened after an update of both Docker desktop and MacOS

macOS Version: 13.0.1
Intel chip or Apple chip: Intel
Docker Desktop Version: 4.14.0

Output of `/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] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[FAIL] DD0017: can a VM be started? vm has not started: vm has not started
[FAIL] DD0016: is the LinuxKit VM running? vm is not running: vm has not started
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[FAIL] DD0015: are the binary symlinks installed? looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[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?
[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?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[WARN] DD0017: can a VM be started? vm has not started: vm has not started
[WARN] DD0016: is the LinuxKit VM running? vm is not running: vm has not started
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[WARN] DD0015: are the binary symlinks installed? looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?

Please note the following 3 warnings:

1 : The check: can a VM be started?
    Produced the following warning: 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.

2 : The check: is the LinuxKit VM running?
    Produced the following warning: vm is not running: vm has not started

The Docker engine runs inside a Linux VM. Therefore the VM must be running.

3 : The check: are the binary symlinks installed?
    Produced the following warning: looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory

The symlinks to the docker CLI etc are needed for docker commands to work.

Please investigate the following 2 issues:

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.

2 : The test: are the binary symlinks installed?
    Failed with: looking for /usr/local/bin/docker-index: lstat /usr/local/bin/docker-index: no such file or directory

The symlinks to the docker CLI etc are needed for docker commands to work.

Steps to reproduce the behavior

Update MacOS to 13.0.1
Update Docker Desktop to 4.14.0
Start Docker Desktop and wait

ajslater commented 1 year ago

Reverting to 4.12 will allow it to run.

stawiski commented 1 year ago

Had the same issue and can confirm reverting to 4.12 as a workaround.

vvilelaj commented 1 year ago

Same here. It worked for me too. Downgrade to 4.12

makotore commented 1 year ago

Workaround to downgrade to 4.12.0 works but ideally would like the fix to be applied to the latest version. I am reporting that the same issue is also on the following docker desktop versions

version 4.14.1
version 4.15.0

tomdotorg commented 1 year ago

Same here. Diagnostic code is 24F709B3-2F2A-4FD6-8AA5-88BD2E3C7BEE/20230126145755

Where do I get 4.12.0?

makotore commented 1 year ago

Same here. Diagnostic code is 24F709B3-2F2A-4FD6-8AA5-88BD2E3C7BEE/20230126145755

Where do I get 4.12.0?

You can get version/4.12.0 from here https://docs.docker.com/desktop/release-notes/

makotore commented 1 year ago

I just reporting that we still see the issue on the following versions as well

version/4.16.0
version/4.16.1
version/4.16.2

Any pointers into fixing this other than downgrading are appreciated

nothing2obvi commented 1 year ago

For me, Docker Desktop for Mac 4.12 is indeed more stable but all my containers do slow down significantly and are sometimes unreachable when there is high network activity.

docker / for-mac