Repository navigation
Description
Summary
Update the macOS/Lima golden-image builder from Ubuntu 24.04 LTS to Ubuntu 26.04 LTS. This is a Lima guest-image change; the Firecracker image source is separate.
Current behavior
src/lima.rs selects Ubuntu 24.04 cloud images for arm64 and amd64 when it builds a golden image. The resulting disk is reused by new instances. The image-staleness check compares the provision script and other metadata but does not include the Ubuntu source image version, so changing only the cloud-image URLs would leave an existing cached golden image on 24.04 after coop setup.
Newly discovered Lima dependency
The full macOS/Lima integration run for PR #618 fails before creating the builder VM when the host has Lima 1.0.2. Lima rejects the generated template with:
field `param` key "internal_netplanOptional" is not used in any provision, probe, copyToHost, or portForward
internal_netplanOptional is a Lima-internal parameter consumed by its cidata netplan template. Support for it, including the validator exception and the Ubuntu 26.04 first-boot NIC-rename workaround, was introduced in Lima 2.1.3. Older Lima releases do not recognize the parameter and also lack the corresponding cidata behavior, so simply omitting the parameter is not a compatible fallback.
This update therefore introduces a macOS host dependency on Lima 2.1.3 or newer, unless coop implements and maintains an equivalent workaround itself. The Firecracker full integration suite is unaffected and passed on PR #618 (613 passed, 0 failed, 12 expected skips).
Proposed work
- Select Ubuntu 26.04 LTS cloud images for both supported Lima architectures and record the source image identity in the image recipe or metadata used by setup's rebuild decision.
- Carry over Lima's Ubuntu 26.04 template workaround,
param.internal_netplanOptional: "true", to the builder and fast-start templates. - Raise coop's Lima prerequisite to 2.1.3 or newer. Update the runtime prerequisite check and documentation so an older
limactlfails early with an actionable upgrade message instead of failing during builder startup. - Verify the base package set, Docker and GitHub CLI repositories, agent installers, and built-in profiles on the new image. Check that the generated fast-start template and a fresh instance boot correctly.
- Update documentation that names Ubuntu 24.04 and explain what happens to cached golden images and existing instance disks. Existing instances should not be described as upgraded merely because the default builder image changes.
Acceptance criteria
- Hosts with Lima older than 2.1.3 receive an early, accurate prerequisite error with upgrade guidance.
- A fresh macOS/Lima
coop setupusing Lima 2.1.3 or newer builds and boots an Ubuntu 26.04 golden image on supported architectures. - Re-running setup with a cached Ubuntu 24.04 golden image detects the source-image change and rebuilds or gives explicit, accurate rebuild guidance; it does not silently report that image as current.
- The macOS/Lima integration suite covers setup, first instance boot, SSH, agent bootstrap, workspace transfer, stop, and restart using the new image.
- Documentation distinguishes the new default for future images from existing instance disks, which retain their current OS until explicitly recreated or upgraded.
References:
Activity