search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 118 forks source link

After upgrading to 4.33.0 (160616), now crashes with "process terminated unexpectedly: accepting AF_VSOCK connection: AF_VSOCK listener closed" #7383

Open rpeck opened 1 month ago

rpeck commented 1 month ago

Description

Docker Desktop was working on my M3 Max MBP (96GB ram, ~160GB disk free).

I upgraded in-app to 4.33.0 (160616). Now the daemon won't start. I get this in the dialog:

running engine: waiting for the Docker API: engine linux/virtualization-framework failed to run: running VM: com.docker.virtualization: process terminated unexpectedly: accepting AF_VSOCK connection: AF_VSOCK listener closed

My diagnostics ID is: 56E4566F-162A-4324-A824-B145A2B81FF3/20240810011527

HALP! :-)

Reproduce

  1. Start up Docker Desktop after a clean reboot.
  2. Observe the error dialog.
  3. Weep.

Expected behavior

Uh, not crashing?

docker version

Version:           27.1.1
 API version:       1.46
 Go version:        go1.21.12
 Git commit:        6312585
 Built:             Tue Jul 23 19:54:12 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

docker info

Client:
 Version:    27.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1-desktop.1
    Path:     /Users/rpeck/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1-desktop.1
    Path:     /Users/rpeck/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     /Users/rpeck/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     /Users/rpeck/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/rpeck/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/rpeck/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/rpeck/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/rpeck/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/rpeck/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.11.0
    Path:     /Users/rpeck/.docker/cli-plugins/docker-scout

Server: (hangs)

Diagnostics ID

56E4566F-162A-4324-A824-B145A2B81FF3/20240810011527

Additional Info

No response

vicentematus commented 1 month ago

[!WARNING] This will delete your containers. Please expect breaking changes.

BREAKING CHANGES: On MacOs, I fixed the error running:

rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker
rm -rf Library/Application\ Support/Docker\ Desktop

Based on the following issue https://github.com/docker/for-mac/issues/6135#issuecomment-1406951111

macstainless commented 1 month ago

I'm encountering the SAME error message on my side. After a few days of Docker chugging along, the entire thing errors out and the entire Docker engine + containers are unresponsive. Has been happening for nearly a month now.

I get this error:

running engine: engine linux/virtualization-framework failed to run: running VM: com.docker.virtualization: process terminated unexpectedly: accepting AF_VSOCK connection: AF_VSOCK listener closed

Intel Mac hardware, Docker Engine: 27.1.1, Docker version 4.33.0 (160616).

Diagnostic ID: 75C47FAE-FA34-4D49-8E5F-EB781AB630B0/20240812123725

wwc-dlemons commented 1 month ago

I'm encountering the same issue. I was on 4.29.0 and on nearly every docker start up I have to go to ~/Library/Group Containers/group.com.docker/settings.json and remove the JetBrains Rider path from the filesharingDirectories just to get Docker up and running. I upgraded today to 4.33.0 and i'm still having the same issue, but now upon me adding back the Rider file path and attempt to lift the container it now gives me the same error OP is getting.

rpeck commented 1 month ago

On MacOs, I fixed the error running:

rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker
rm -rf Library/Application\ Support/Docker\ Desktop

Based on the following issue #6135 (comment)

Hm.

Docker is running now, but I've lost the container I had set up.

This is a real drag. Warning to those who come after: this will blow away your containers. I've lost a few hours of work. Yay.

vicentematus commented 1 month ago

On MacOs, I fixed the error running:

rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker
rm -rf Library/Application\ Support/Docker\ Desktop

Based on the following issue #6135 (comment)

Hm.

Docker is running now, but I've lost the container I had set up.

This is a real drag. Warning to those who come after: this will blow away your containers. I've lost a few hours of work. Yay.

Damn, sorry :(. I will add an alert for my comment. I didn't expected breaking changes

MilanVilov commented 3 weeks ago

On MacOs, I fixed the error running:

rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker
rm -rf Library/Application\ Support/Docker\ Desktop

Based on the following issue #6135 (comment)

Hm.

Docker is running now, but I've lost the container I had set up.

This is a real drag. Warning to those who come after: this will blow away your containers. I've lost a few hours of work. Yay.

This solved the problem, thank you 🙇

anqus commented 3 weeks ago

I'm encountering the same issue. I was on 4.29.0 and on nearly every docker start up I have to go to ~/Library/Group Containers/group.com.docker/settings.json and remove the JetBrains Rider path from the filesharingDirectories just to get Docker up and running. I upgraded today to 4.33.0 and i'm still having the same issue, but now upon me adding back the Rider file path and attempt to lift the container it now gives me the same error OP is getting.

Same problem here, can't debug anything in Rider currently.

belm0 commented 1 week ago

Deleting Library files and filesharingDirectories did not help in my case. For me it seems to be related to heavy load in the container, as reported in https://github.com/docker/for-mac/issues/7381

avo-sepp commented 1 week ago

This happens to me after Docker freezes up doing something, sometimes it's building, sometimes it's pushing a container. Then Docker freezes. When I stop the operation with CTRL+C in terminal. Then Docker is non-responsive. Restarting Docker gives the AF_VSOCK error. The only solution I have is to re-install Docker Desktop from scratch. Repeating the operation will break Docker again.

There is definitely some operation or action which breaks this connection in an unfixable manner.

I am on a MacBook Pro, 16GB RAM, M1 Pro chip.

Diagnostics ID: 76782BD3-97D1-4BBD-8F60-F33B84574B4C/20240905170703

tanel commented 4 days ago

Experienced the same issue, after upgrade Docker did not start and gave the AF_VSOCK error. Increasing memory and swap in the settings fixed the issue.