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 or delete them. You can also author images manually to reference existing AMIs, GCE images, or Docker containers that you manage outside Murmur.
Fields
Exactly one of
aws, gce, or docker must be set.
AWS source fields
Setaws to reference one or more AMIs:
GCE source fields
Setgce to reference a GCE disk image or image family:
Docker source fields
Setdocker to reference a container image:
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 viamurmur set.
Examples
Hand-authored GCE image
Hand-authored AWS image
Hand-authored Docker 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
Related
- Images — concept overview
- Recipes — the provisioning template that produces baked images
- Workspaces — the resource that references an image via
image_ref murmur set— CLI command for creating and updating catalog resourcesmurmur get— CLI command for reading catalog resourcesmurmur bake— bakes images from recipes