Found during the plans#36 smoke legs. When the registry lacks the current content tag, ensure_image! falls back from pull to build; on the agent's colima engine the build immediately dies with:
ERROR: BuildKit is enabled but the buildx component is missing or broken.
Two angles, either or both:
- The colima provisioner (
dev runner register --org --ai-flow) should install the buildx plugin into the agent's docker so builds are possible (brew's docker-buildx serves the human's Docker Desktop; the agent's colima docker has no plugins dir populated).
- Arguably the agent identity should never build at all — it cannot hold
build_secrets, and Path B (registry pull) is its designed route. A cache+registry double miss under the agent could fail with a message that says "the registry lacks ; a provisioning machine must run dev up to build and publish it" instead of a buildx stack trace.
Observed live: agent dev test-game in cellbound-3d → registry lacked content-4864a449b5a1 (engine bump 5.8.0-wine-7 minted a tag no machine had built) → build fallback → buildx error.
Found during the plans#36 smoke legs. When the registry lacks the current content tag,
ensure_image!falls back from pull to build; on the agent's colima engine the build immediately dies with:Two angles, either or both:
dev runner register --org --ai-flow) should install the buildx plugin into the agent's docker so builds are possible (brew'sdocker-buildxserves the human's Docker Desktop; the agent's colima docker has no plugins dir populated).build_secrets, and Path B (registry pull) is its designed route. A cache+registry double miss under the agent could fail with a message that says "the registry lacks ; a provisioning machine must rundev upto build and publish it" instead of a buildx stack trace.Observed live: agent
dev test-gamein cellbound-3d → registry lackedcontent-4864a449b5a1(engine bump 5.8.0-wine-7 minted a tag no machine had built) → build fallback → buildx error.