Expected behavior
After pausing Docker Desktop and then shutting down macOS via the Apple menu, the next boot should auto-start Docker Desktop cleanly without a "Lingering processes detected" dialog.
Actual behavior
On every boot following a "Pause → macOS Shutdown" sequence, Docker Desktop shows:
Docker Desktop - Lingering processes detected
One or more running processes can prevent Docker Desktop startup:
The referenced PID does not exist on the freshly booted system (ps -p <N> returns nothing). The actual Docker Desktop process tree from the current autostart is running under different PIDs (verified: dialog reported pid 823, but com.docker.backend --autostart and its children were running as pids 826/843/844/874… all started ~5 s after boot).
This looks like a stale entry in Docker Desktop's lockfile/state under ~/Library/Containers/com.docker.docker/Data/ that is not cleared when the app is in the Paused state at shutdown time — the clean-quit handler never runs because the system shutdown bypasses it.
Clicking "Stop processes" clears it and Docker starts normally.
Information
- macOS: 26.4.1 (build 25E253), Darwin 25.4.0
- Hardware: Apple Silicon (M5)
- Docker Desktop: 4.71.0
- Reproduces: every boot after Pause → Shutdown
Steps to reproduce
- Start Docker Desktop, let it reach Running.
- Click whale icon → Pause.
- Apple menu → Shut Down… (do NOT Quit Docker first).
- Power on the Mac, log in.
- Docker Desktop autostarts and shows the "Lingering processes detected" dialog with a PID that is not actually running.
Workaround
Quit Docker Desktop (whale → Quit) before shutdown instead of leaving it Paused. The dialog does not appear when shut down from the Quit state.
Notes
Happy to attach Gather diagnostics output if useful — let me know.
Expected behavior
After pausing Docker Desktop and then shutting down macOS via the Apple menu, the next boot should auto-start Docker Desktop cleanly without a "Lingering processes detected" dialog.
Actual behavior
On every boot following a "Pause → macOS Shutdown" sequence, Docker Desktop shows:
The referenced PID does not exist on the freshly booted system (
ps -p <N>returns nothing). The actual Docker Desktop process tree from the current autostart is running under different PIDs (verified: dialog reported pid 823, butcom.docker.backend --autostartand its children were running as pids 826/843/844/874… all started ~5 s after boot).This looks like a stale entry in Docker Desktop's lockfile/state under
~/Library/Containers/com.docker.docker/Data/that is not cleared when the app is in the Paused state at shutdown time — the clean-quit handler never runs because the system shutdown bypasses it.Clicking "Stop processes" clears it and Docker starts normally.
Information
Steps to reproduce
Workaround
Quit Docker Desktop (whale → Quit) before shutdown instead of leaving it Paused. The dialog does not appear when shut down from the Quit state.
Notes
Happy to attach
Gather diagnosticsoutput if useful — let me know.