make preflight

Run the host pre-flight checks only. No container, no changes.

---

Usage

make preflight

What it checks

The host-side scripts/preflight_cli.sh, without touching any container.

1. Docker is installed.
2. The Docker daemon is reachable without sudo.
3. Docker Compose v2 (docker compose) is available.
4. ~/.gitconfig and ~/.ssh are sane for bind-mounting.
5. The workspace .env. Duplicate/malformed keys, stale host path, dangling product, drift from the template (same logic as make env-check).

Exit code is 1 if a hard problem is found, 0 otherwise.

A workspace .env that does not exist yet is not a failure here. Before the first make setup there is no .env, so the pre-flight prints an info line and passes:

  • .env not created yet (make setup creates it from .env.example)

Only the standalone make env-check treats a missing .env as an error.

When to use

To diagnose your machine before running make setup, e.g. to confirm Docker is up and your .env is healthy without starting anything.

The lifecycle targets (setup, docker-up, cli) run this pre-flight automatically. make preflight is just the standalone, read-only version.

Related

• make env-check. Only the .env portion.
• splent doctor. Deeper diagnostics from inside the container.