murmur bakes ls

Lists image bake workflows for the current tenant. Shows each bake’s phase, recipe, environment, placement, the service profile and cloud service account it ran under, image hash, and timing. By default, includes completed, failed, and cached bakes: use --all=false to show only queued and running bakes. The PROFILE and ACCOUNT columns record the identity a bake actually ran under. Together with ENV and PLACEMENT they are exactly the arguments murmur bake needs, so a past bake can be reproduced by copying them into a new command.

Synopsis

murmur bakes ls [flags]

Arguments

Name	Type	Required	Description
`--all`	bool	no	Include completed, failed, and cached bakes. Set `--all=false` to show only queued and running bakes. Default: `true`.
`--placement`	string	no	Filter results to a specific placement.
`--environment`	string	no	Filter results to a specific environment.
`--page-size`	int	no	Number of results per page. Must be between 1 and 100. When omitted, the server uses `25`.
`--page-token`	string	no	Opaque token for fetching the next page of results. Omit for the first page.
`--full-hash`	bool	no	Show the full image hash instead of the first 12 characters. Default: `false`.

Output

A table with the following columns:

Column	Description
`PHASE`	Current phase of the bake: `queued` (started, waiting for its first step), `running`, `completed`, `failed`, or `cached`.
`SCOPE`	The target scope where the image is created (e.g., a cloud project).
`HASH`	Image hash: truncated to 12 characters by default. Use `--full-hash` for the full value.
`RUN ID`	Bake run identifier, truncated to 8 characters.
`ENV`	Environment name.
`PLACEMENT`	Placement name.
`PROFILE`	Service profile whose credentials the bake ran under. `-` when the bake predates provenance recording.
`ACCOUNT`	Cloud service account the bake VM was pinned to. `-` when the placement has no service-account bindings, or when the bake predates provenance recording.
`STARTED`	Timestamp when the bake started (RFC 3339, UTC). `-` if not yet started.
`COMPLETED`	Timestamp when the bake finished (RFC 3339, UTC). `-` if still running.
`RECIPE`	Recipe name.
`ERROR`	Error message if the bake failed. Empty otherwise.

When additional pages exist, the output includes a next-page token and a follow-up command.

Examples

List all bakes

murmur bakes ls

PHASE      SCOPE        HASH          RUN ID    ENV      PLACEMENT    PROFILE        ACCOUNT                                          STARTED               COMPLETED             RECIPE      ERROR
completed  acme-agents  9f86d0818849  a1b2c3d4  staging  us-central1  image-builder  murmur-bake@acme-agents.iam.gserviceaccount.com  2026-05-14T10:10:00Z  2026-05-14T10:25:12Z  my-recipe
running    acme-agents  7c211433f020  e5f6a7b8  prod     us-east1     image-builder  murmur-bake@acme-agents.iam.gserviceaccount.com  2026-05-14T10:40:00Z  -                     my-recipe
failed     acme-agents  2cf24dba5fb0  c9d0e1f2  staging  us-central1  -              -                                                2026-05-14T08:35:00Z  2026-05-14T08:42:45Z  old-recipe  script exited with code 1

Reproduce a past bake

A row with a recorded PROFILE carries everything murmur bake needs. Copy its ENV, PLACEMENT, PROFILE, and ACCOUNT into a new command:

murmur bake my-recipe \
  --environment staging \
  --placement us-central1 \
  --service-profile image-builder \
  --service-account murmur-bake@acme-agents.iam.gserviceaccount.com

Where a column reads -, there is no value to copy:

ACCOUNT is -: omit --service-account. If the placement has service-account bindings, the bake fails with service_account is required and names the placement, so you learn which binding to pin rather than building under the wrong identity.
PROFILE is -: the bake predates provenance recording, and the row alone cannot reproduce it. - is not a profile name; choose one you are allowed to borrow with murmur spawn-profiles, which is the same service-profile.assume authority a bake requires.

Show only queued and running bakes

murmur bakes ls --all=false

Filter by placement

murmur bakes ls --placement us-central1

Filter by environment

murmur bakes ls --environment staging

Show full image hashes

murmur bakes ls --full-hash

Paginate through results

murmur bakes ls --page-size 10

PHASE      SCOPE        HASH          RUN ID    ENV      PLACEMENT    PROFILE        ACCOUNT                                          STARTED               COMPLETED             RECIPE      ERROR
...

Next page: eyJsYXN0X2lkIjoiMTAifQ==
Run with --page-token=eyJsYXN0X2lkIjoiMTAifQ== to fetch the next page.

murmur bakes ls --page-size 10 --page-token=eyJsYXN0X2lkIjoiMTAifQ==

Errors

Code	Meaning	What to do
none	`--page-size must be in [1, 100], got N`: the CLI rejects the page size before contacting the server.	Use a page size between 1 and 100.
`INVALID_ARGUMENT`	`invalid page_token`: the page token is malformed.	Pass the token exactly as printed by the previous page, or omit `--page-token`.
`UNAUTHENTICATED`	Identity token is missing or expired.	Run `murmur login`, or check your `murmur.local.yaml` configuration.

Images: concept overview of the two-layer image model
Recipe: what a recipe defines
Custom images guide: end-to-end walkthrough of building custom images
murmur bake: start a bake

Getting Started

Core Concepts

Guides

murmur bakes ls

Synopsis

Arguments

Output

Examples

List all bakes

Reproduce a past bake

Show only queued and running bakes

Filter by placement

Filter by environment

Show full image hashes

Paginate through results

Errors

​Synopsis

​Arguments

​Output

​Examples

​List all bakes

​Reproduce a past bake

​Show only queued and running bakes

​Filter by placement

​Filter by environment

​Show full image hashes

​Paginate through results

​Errors

​Related

Synopsis

Arguments

Output

Examples

List all bakes

Reproduce a past bake

Show only queued and running bakes

Filter by placement

Filter by environment

Show full image hashes

Paginate through results

Errors

Related