Will this install Docker for me?

Not in v1. Empty machine still uses the Desktop guide or the copied Colima brew line. Recover attaches to an engine you already installed.

Does dc-doctor start Docker?

No. Doctor is read-only. dc-recover is the mutate door.

Recover asks you to keep this CLI engine, switches context, and stops only the extra (colima stop or quit Docker.app). It does not disable systemd.

guide / stuck· 2026-08-22

One next step. Then retry.

dc-recover is the day-2 mutate door when the engine you already have is the wall.

dc-recover                 # this folder; print one next command
dc-recover --yes           # apply that command (allowlisted)
dc-recover --json          # agents
dc-recover --report ./out  # redacted bundle for a GitHub issue

You already have	`--yes` may
Desktop or Colima, stopped	start that engine
Two live engines	`docker context use` + stop the extra
Bad `DOCKER_HOST` / context	point the CLI at the existing engine
Linux permission denied	`usermod -aG docker`, then re-login
Disk full	`dc-prune --yes`; Colima guest still full → `--grow-disk`
Host ready, folder has no config	`dc-try` (sandbox + default localhost ports; `--yes` applies `try_sandbox`)

It does not run docker system prune -af --volumes, stop unlabeled port holders, systemctl disable --now, or edit ~/.zshrc.

No engine at all? See No Docker engine. Diagnose only? dc-doctor.

FAQ

Will this install Docker for me?: Not in v1. Empty machine still uses the Desktop guide or the copied Colima brew line. Recover attaches to an engine you already installed.
Does dc-doctor start Docker?: No. Doctor is read-only. dc-recover is the mutate door.
Two engines live?: Recover asks you to keep this CLI engine, switches context, and stops only the extra (colima stop or quit Docker.app). It does not disable systemd.

Broke something?report it