David Ibia 74a718efa8 fix(docker-nuke): give accurate recovery advice when the daemon does not return ...

The failure path advised --deep and a disk-space check regardless of cause.
On the first live run that was wrong on both counts: 101 GiB were free and
--deep was irrelevant. Docker Desktop had crashed on startup, and the actual
fix was launching it from the Dock.

Branch the advice on whether any Docker process survived the relaunch. No
survivors means the app did not stay up, which no programmatic relaunch can
work around; survivors mean it is up but not answering yet.

2026-07-20 16:51:16 +01:00

..

bin

fix(docker-nuke): give accurate recovery advice when the daemon does not return

2026-07-20 16:51:16 +01:00