Builds

BuildService (dodil.ignite.v1.BuildService) runs remote container image builds with Kaniko  from a Dockerfile. You supply the build context one of three ways — an inline zip, a previously uploaded context, or a git repo — and the result is an image pushed to your organization’s registry, ready for an image-mode app version in Compute to run.

Builds are asynchronous: CreateBuild returns a build_id immediately, the build moves through PENDING → RUNNING → SUCCEEDED | FAILED | CANCELLED, and you follow progress with streaming logs.

In this section

• Quickstart — build an image from a local Dockerfile and run it on Compute
• How Builds Work — context sources, the build lifecycle, credentials, and the Compute hand-off
• CLI Guide — the dodil ignite build command group
• API Reference — every BuildService RPC, with HTTP + gRPC contracts

At a glance

• Builder — Kaniko, from a Dockerfile. (Compute can auto-detect a builder for source without a Dockerfile; standalone builds here require one — see How Builds Work.)
• Context — inline zip (< 4 MB), an uploaded context_id for larger trees, or a git URL + ref (no upload).
• Output — an image pushed to your org-scoped registry; the full imageRefs are recorded on the build.
• Credentials — registry and git credentials are stored per organization with SaveBuildSecrets (see Secrets for the distinct named-slot model Compute BYOI uses).

See also

• Quickstart · How Builds Work · CLI Guide · API Reference
• Compute — image-mode versions that run built images
• Secrets — credentials referenced by builds and deploys
• Conventions — transport, auth, streaming
• CLI Basics