Skip to main content
An image is a catalog resource that points to a runnable artifact on a specific substrate: an AWS AMI or a GCE disk image. Each workspace references one image via its image_ref field. Images are typically produced by the bake process. When you bake a recipe, the platform executes it against a base image and writes the resulting image back to the catalog with provenance metadata. Baked images are immutable: you cannot update them. Deleting a baked image with murmur rm image <name> also deletes its cloud artifact (the GCE image or the AMIs). Deleting a hand-authored image removes only the catalog record. You can also author images manually to reference existing AMIs or GCE images that you manage outside Murmur.

Fields

A new baked image inherits its recipe’s workspace_use policy. Reusing an existing baked image preserves its stored policy. Baked records are immutable to tenant callers, including their admission policy. Exactly one of aws or gce must be set.

AWS source fields

Set aws to reference one or more AMIs:
AMIs are region-bound. A baked image has one entry in ami_ids: the region the bake ran in. If a workspace references this image and its placement targets a different region, spawn fails.

GCE source fields

Set gce to reference a GCE disk image or image family:

Provenance fields

Provenance is present on baked images and records what produced them. It is set automatically by the bake process and cannot be set via murmur set.

Examples

Hand-authored GCE image

Hand-authored AWS image

Baked image (generated by the platform)

Baked images appear in the catalog after a successful bake. Their names are generated and they carry provenance metadata:

Listing images

Reading a single image

Errors