Why
First-ever Docker Desktop start on AV-heavy corporate laptops routinely takes 5–10 minutes (WSL bootstrap, image unpack, onboarding). The installer waits 60×3s = 3 minutes, then hard-exits with "Re-run this script once Docker is ready" — turning a normal cold start into a failed install + manual re-paste of the one-liner. Observed as a recurring "wait, then re-run" loop on hospital installs.
Where
scripts/install-k8s.ps1 (v1.9.6): Install-DockerDesktop wait loop L500–533.
Scope
- Extend the wait to ~10 minutes with honest periodic status ("Docker is still starting — 4 min elapsed; first start can take up to 10").
- Keep waiting through the engine's transitional states; only fail on a genuinely stuck/errored engine, with the specific reason (license window open, WSL prompt, service dead) where detectable.
Acceptance criteria
- A cold start taking >3 min completes without any re-run.
- Timeout message names the observed engine state, not a generic retry request.
Why
First-ever Docker Desktop start on AV-heavy corporate laptops routinely takes 5–10 minutes (WSL bootstrap, image unpack, onboarding). The installer waits 60×3s = 3 minutes, then hard-exits with "Re-run this script once Docker is ready" — turning a normal cold start into a failed install + manual re-paste of the one-liner. Observed as a recurring "wait, then re-run" loop on hospital installs.
Where
scripts/install-k8s.ps1(v1.9.6):Install-DockerDesktopwait loop L500–533.Scope
Acceptance criteria