CLI Guide — dodil ignite build
The build command group drives BuildService from the terminal. For install, authentication, global flags (--output, --api-endpoint, --token, --debug), and exit codes, see CLI Basics.
Commands
| Command | What it does |
|---|---|
dodil ignite build create <name> | Start a build. |
dodil ignite build upload | Upload a large context, get a context_id. |
dodil ignite build get <build-id> | Show a build’s status, image refs, and metrics. |
dodil ignite build list | List recent builds. |
dodil ignite build logs <build-id> | Stream build logs. |
dodil ignite build cancel <build-id> | Cancel an in-flight build. |
dodil ignite build secrets set | Store registry / git / build credentials for the org. |
create
dodil ignite build create my-image --context . --tag latest --build-arg VERSION=1.2.3| Flag | Default | Description |
|---|---|---|
-c, --context | . | Local directory to use as the build context (tarred and sent inline; must be < 4 MB). |
-f, --dockerfile | Dockerfile | Dockerfile path relative to the context root. |
-t, --tag | latest | Image tag. Repeatable. |
--build-arg | — | KEY=VALUE Docker build arg. Repeatable. |
--no-cache | false | Disable layer caching. |
--timeout | server default | Build timeout, in seconds. |
--context-id | — | Use a context from build upload instead of the local directory. |
--git-url | — | Build from a git repo instead of a local context. |
--git-ref | main | Git branch, tag, or SHA (with --git-url). |
--git-dir | — | Subdirectory within the repo to use as the context root. |
Source precedence: --context-id → --git-url → the local --context directory. The command prints a build_id; follow it with build logs.
If the context has no Dockerfile, the CLI scaffolds a starter one for common stacks before submitting. Commit your own
Dockerfilewhenever you need control over the image.
upload
For contexts larger than the 4 MB inline limit. Streams the folder to the server and prints a context_id to pass to build create --context-id.
dodil ignite build upload --folder . --name my-imageget / list
dodil ignite build get <build-id>
dodil ignite build list --status running --limit 20list accepts --status (pending, running, succeeded, failed, cancelled) and --limit (default 20).
logs
dodil ignite build logs <build-id> --followStreams the build’s output to stdout until it reaches a terminal state.
cancel
dodil ignite build cancel <build-id>secrets set
Stores credentials for the organization (used by every subsequent build — see How Builds Work).
# Registry auth (push targets / private base images)
dodil ignite build secrets set --registry ghcr.io --auth <base64-auth>
# Git credentials for private repos
dodil ignite build secrets set --git-username <user> --git-password <token>
# Extra build secrets, exposed as build args
dodil ignite build secrets set API_KEY=... DB_URL=...See also
- Quickstart — the end-to-end flow
- How Builds Work — context sources, lifecycle, credentials
- API Reference — the underlying RPCs
- CLI Basics — auth, global flags, exit codes