Why not update in place
- In-place updates to some versions currently fail inside VMs. Updates to macOS 15.x and 26.x targets either never finish booting or leave the VM with capped memory. A workaround exists, but it adds steps to every update. See the known issue in the Orka compatibility matrix.
- Resized VMs can fail to update. If your image was grown with
orka vm resize, a macOS update inside it might fail. See the limitations in Apple silicon Mac servers in Orka. - An updated image carries its history. Leftover files, caches, and settings from every earlier version stay in the image. A rebuild contains only what your build script puts there.
Script the image build
Keep the steps that turn a base image into your CI image in a script or a Packer template: install Xcode and toolchains, configure macOS, then push. A macOS update then becomes:- Point the build at the base image for the new version, such as
ghcr.io/macstadium/orka-images/tahoe:<TAG>, orghcr.io/macstadium/orka-images/golden-gate:latestfor macOS 27. The orka-images repository lists the available images and tags. - Run the build and push the result to a new versioned tag.
- Deploy a VM from the new tag and run real jobs on it.
- Point your pipelines at the new tag.

