After upgrading to 4.33.0 (160616), now crashes with "process terminated unexpectedly: accepting AF_VSOCK connection: AF_VSOCK listener closed"
### 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 ```bash 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 ```bash 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
Posted by rpeck on Aug 10, 2024, 1:43 AM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
After upgrading to 4.33.0 (160616), now crashes with "process terminated unexpectedly: accepting AF_VSOCK connection: AF_VSOCK listener closed"
### 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 ```bash 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 ```bash 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
Comments (0)
No comments yet. Start the discussion.