guide / no-docker· 2026-08-20
Helpers install. Docker is still your job.
dc-cli needs a Docker engine. It does not install one for you. If Desktop or Colima is already installed, dc-recover --yes / TUI [f] can start it.
What you will see
| Surface | Behavior |
|---|---|
install.sh |
Helpers still install. Readiness block explains what is missing. |
dc doctor |
Blocker on docker_cli / docker_daemon with a host code and remediation. |
dc up |
Refuses early with the same recovery text. |
dc |
Blocked setup screen: [f] try fix (existing engine), [d] Desktop guide, [c] copy Colima, [r] retry, [q] quit. |
Codes
docker_cli_missing—dockernot on PATHdocker_engine_missing— no engine evidence on the machinedocker_engine_stopped— engine present but not reachabledocker_permission_denied— socket permission / group issuedocker_context_invalid— bad context /DOCKER_HOSTdocker_split_brain— more than one live engine (dc-recover --yesordc-engine --fix)
Beginner path
- Install Docker Desktop
- Wait until it is ready
dc-doctordcordc up
Lightweight macOS path
brew install docker colima
colima start
dc doctor
dc
One live engine only — Colima or Desktop, not both.
FAQ
- Does install fail without Docker?
- No. Helpers install. Machine readiness is reported separately. Day-2 diagnosis is dc-doctor.
- Will dc-cli start Docker for me?
- If an engine is already installed, dc-recover --yes / TUI [f] can start it. It still never auto-installs Desktop or Colima.
- What does the TUI show?
- A blocked setup screen. Engine already there — [f] try fix. Empty machine — [d] Desktop guide, [c] copy Colima setup. [r] retry, [q] quit.
Broke something?report it