Docker / Docker

Docker Desktop M1/M2 macOS Kernel Panic Crashes After Update — ext4_es_scan / kswapd Freezes VM

Fix Docker Desktop kernel panics and startup crashes on Apple Silicon Macs after version updates, specifically ext4 filesystem scanner and swap daemon causing complete VM freezes Includes evidence for Docker troubleshooting demand.

Source-backed Last updated June 1, 2026 3 sources Needs local verification

Category: Docker
Error signature: Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: June 1, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Docker, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic is a Docker failure pattern reported for developers trying to fix docker desktop kernel panics and startup crashes on apple silicon macs after version updates, specifically ext4 filesystem scanner and swap daemon causing complete vm freezes. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Multiple open GitHub issues on docker/for-mac (#7834, #7877, #7825, #7664, #7828) showing a pattern of kernel panic crashes affecting M1/M2 Macs on recent Docker Desktop versions (4.41+ through 4.73.0). This is distinct from the covered 'cannot connect to daemon' error — these are hard crashes requiring restart/reinstall. Enterprise impact: CI/CD pipelines, local development blocked entirely. High commercial value as Docker Desktop has paid enterprise tier.

Common causes

Multiple open GitHub issues on docker/for-mac (#7834, #7877, #7825, #7664, #7828) showing a pattern of kernel panic crashes affecting M1/M2 Macs on recent Docker Desktop versions (4.41+ through 4.73.0). This is distinct from the covered 'cannot connect to daemon' error — these are hard crashes requiring restart/reinstall. Enterprise impact: CI/CD pipelines, local development blocked entirely. High commercial value as Docker Desktop has paid enterprise tier.

Quick fixes

Confirm the exact error signature matches Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic.
Check the Docker account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic exactly before applying the quick fix.
Compare the failing environment with Docker versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic mean in Docker?

Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic indicates the workflow described by "Docker Desktop M1/M2 macOS Kernel Panic Crashes After Update — ext4_es_scan / kswapd Freezes VM" failed in a Docker context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic?

Check whether this cause matches your environment: Multiple open GitHub issues on docker/for-mac (#7834, #7877, #7825, #7664, #7828) showing a pattern of kernel panic crashes affecting M1/M2 Macs on recent Docker Desktop versions (4.41+ through 4.73.0). This is distinct from the covered 'cannot connect to daemon' error — these are hard crashes requiring restart/reinstall. Enterprise impact: CI/CD pipelines, local development blocked entirely. High commercial value as Docker Desktop has paid enterprise tier.

Is the Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic guidance source-backed?

The "Docker Desktop M1/M2 macOS Kernel Panic Crashes After Update — ext4_es_scan / kswapd Freezes VM" page is labeled source-backed. It has 3 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic?

For "Docker Desktop M1/M2 macOS Kernel Panic Crashes After Update — ext4_es_scan / kswapd Freezes VM", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Kernel panic in ext4_es_scan / kswapd freezes entire VM (linuxkit 6.12.76 / Docker Desktop 4.73.0) OR crashes on startup with disk.extend panic?

For "Docker Desktop M1/M2 macOS Kernel Panic Crashes After Update — ext4_es_scan / kswapd Freezes VM", collect the failing Docker command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.