~$dc --help

Task guides. README stays short.

Install, kind, board, doctor, missing Docker, ports, disk, sandbox try. Typedc, then a verb. dc-up still works. Flags:dc --help.

  1. /install

    Install dc-cli

    curl --with-cli installs the latest release: compiled dc-tui and dc-actions. A source install builds both when Go is on PATH; without Go, shell fallback. Then source ~/.bashrc or source ~/.zshrc.

  2. /try

    Sandbox start without config

    dc-try starts a folder that has no .devcontainer and no root compose. External override. No project edits.

  3. /tui

    dc-tui board and keys

    Board for this folder. w lists favorites, then recent folders, including stopped projects, and does not start them. c is opt-in container actions through dc exec --no-start. v keeps the latest 200 session events in memory and refreshes the board.

  4. /stuck

    Stuck: dc-recover

    When Docker or this folder blocks dc-cli, run dc-recover. It prints one next step. --yes applies it if you already have an engine. Doctor stays read-only.

  5. /kind

    Dev Container vs compose

    dc-cli detects this folder. .devcontainer is official CLI. Compose-only uses docker compose or docker-compose. Same keys. No daemon UI.

  6. /doctor

    dc-doctor read-only checks

    dc-doctor diagnoses the engine and workspace without mutating Docker or project files. Human text and --json share one check list.

  7. /no-docker

    No Docker engine

    dc-cli installs without Docker. Installer, doctor, up, and TUI guide recovery. Never auto-installs an engine.

  8. /ports

    Colima ports and host clashes

    dc-forward reconciles owned sidecars (one app or --id). --take-ports stops labeled holders only; unlabeled is report-only.

  9. /disk

    Disk full: dc-df and dc-prune

    When dc-up fails with ENOSPC, run dc-df then dc-prune --yes. Cache/images/nets are engine-wide. Never docker system prune -af --volumes.