Docker Dekstop 4.16.2 stopped

wslawski-printify commented 1 year ago

[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:56A971AF-A569-417E-8AAC-D7F71A30E9F2/20230123092714

Expected behavior

Docker Desktop should be running all the time, not randomly stop.

Actual behavior

Docker Destkop has stopped and I need to reboot to start using it again properly.

Information

macOS Version: 13.1
Intel chip or Apple chip: Apple chip M1 PRO
Docker Desktop Version: 4.16.2

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

Please note the following 4 warnings:

1 : The check: are the LinuxKit services running?
    Produced the following warning: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

2 : The check: is the Docker engine running?
    Produced the following warning: Get "http://ipc/docker": dial unix lifecycle-server.sock: connect: no such file or directory

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

3 : The check: does the Docker API work?
    Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

If the Docker API is not available from the host then Docker Desktop will not work correctly.

4 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: Cannot connect to the Docker daemon at unix://docker.raw.sock. Is the docker daemon running?

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 2 issues:

1 : The test: are the LinuxKit services running?
    Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

2 : The test: are the backend processes running?
    Failed with: 4 errors occurred:
    * vpnkit-bridge is not running
    * com.docker.vpnkit is not running
    * com.docker.driver.amd64-linux is not running
    * com.docker.virtualization is not running

Steps to reproduce the behavior

None, it happens pretty randomly, most of the time when there is some inactivity on my mac. It seemed at first that disabling automatic updates of docker desktop improved a thing for a bit, but after sometime it happened anyway.

This is pretty much continuation of https://github.com/docker/for-mac/issues/6472 which was closed as completed when it's not completed - issue is still happening, at least for me. This is pretty new mac - one month old, and this issue is happening for me from the first day I started working on it.

smshapiro85 commented 1 year ago

Just wanted to report in that 4.17 has completed resolved the issue for me after a week. No sudden "Docker Desktop Has Stopped' issues so far.

wslawski-printify commented 1 year ago

Same here, though I had to restart my mac anyway because it started lagging

smshapiro85 commented 1 year ago

4.17 has been good for a few weeks, up until yesterday where I stumbled upon a blank docker desktop with no containers. I had to completely shut down docker and re-open it, and the containers re-appeared. Really odd. So, overall a huge improvement as I have been able to run solid for weeks, but frustrating that the issue suddenly appeared again. Not sure if anyone else has experienced this with 4.17.

half0wl commented 1 year ago

I have the same issue on Docker Desktop 4.16.2 (95914), macOS Ventura 13.2 (22D49). It happened out of the blue; I didn't do anything out of the norm (no recent OS updates etc.)

$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
...<truncated, same as diagnostics from OP>
Please investigate the following 1 issue:

1 : The test: are the LinuxKit services running?
    Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": dial unix diagnosticd.sock: connect: no such file or directory

These are the only steps that worked for me, requiring a complete wipe of Docker:

Uninstall via:

$ /Applications/Docker.app/Contents/MacOS/uninstall

Re-open Docker Desktop (Applications -> Docker)

After that, I applied the latest update to 4.17.0 (99724) and rebooted for good measure. Everything seems fine now.

Things I've tried in the course of troubleshooting this:

Rebooting multiple times. Didn't work.
rm -rf-ing whatever I find on Google about Docker installations on macOS. Didn't work.
Updating. Nope, the dashboard is blocked by a loading spinner.
Wiping Docker via the UI. Nope - I couldn't clean/purge data, reset to factory defaults, or even uninstall. All actions perform nothing:
- Troubleshoot -> Clean / Purge data -> Click "Delete" on confirmation dialog -> Nothing happens
- Troubleshoot -> Reset to factory defaults -> Click "Yes, reset anyway" on confirmation dialog -> Nothing happens
- Troubleshoot -> Uninstall -> Click "Uninstall" on confirmation dialog -> Nothing happens

Hope this helps someone in the same predicament!

docker / for-mac