Every os-image flavor except two now publishes linux/amd64,linux/arm64 (base, python, python-rt, rt), as do the boot and silkd carriers. The remaining amd64-only pins are:
os-image/browser/platforms — the Dockerfile installs Chrome for Testing from the linux64 archive, and upstream ships no linux/arm64 build.os-image/android/platforms — the flavor is assembled from an amd64 redroid-based ANDROID_BASE_IMAGE.
Both look liftable:
- browser: switch to a Chromium distribution that ships linux/arm64 (e.g. Playwright's chromium builds or Chromium snapshots), selected by
TARGETARCH. Chrome-specific behavior in the smoke test would need a pass.
- android: upstream redroid publishes arm64 images, and the cocoon boot-chain pieces (kernel, agent) already build for arm64 elsewhere in the stack; the base image and any arch-keyed artifacts need
TARGETARCH wiring.
Acceptance: drop the two platforms files (falling back to the default dual-arch matrix in build-os-images), green builds for both platforms, and the browser/android smoke tests passing on an arm64 host.
Every os-image flavor except two now publishes
linux/amd64,linux/arm64(base, python, python-rt, rt), as do the boot and silkd carriers. The remaining amd64-only pins are:os-image/browser/platforms— the Dockerfile installs Chrome for Testing from thelinux64archive, and upstream ships no linux/arm64 build.os-image/android/platforms— the flavor is assembled from an amd64 redroid-basedANDROID_BASE_IMAGE.Both look liftable:
TARGETARCH. Chrome-specific behavior in the smoke test would need a pass.TARGETARCHwiring.Acceptance: drop the two
platformsfiles (falling back to the default dual-arch matrix in build-os-images), green builds for both platforms, and the browser/android smoke tests passing on an arm64 host.