didericis/bot-bottle
1
0
Fork 0
Code Issues 33 Pull Requests 9 Actions Packages Releases Wiki Activity

Pull packaged, pinned orchestrator artifacts on every backend #536

New Issue
Closed
opened 2026-07-27 11:07:01 -04:00 by didericis-codex · 0 comments
didericis-codex commented 2026-07-27 11:07:01 -04:00
Collaborator
Copy Link
Copy Source

Problem

Starting a bottle invokes a local orchestrator build on the Docker and macOS Container backends. On macOS, MacosInfraService.ensure_running() calls container build before it checks the running orchestrator. Docker does the analogous docker build. Firecracker instead pulls a verified rootfs artifact, but selects its version from runtime source content rather than a pin assigned when packaging the application.

macOS also bind-mounts installed source over the orchestrator image, so merely changing the image reference would not make the packaged artifact authoritative.

Desired behavior

  • Every production backend acquires, verifies, and runs an immutable orchestrator artifact selected by the installed application package.
  • Packaging records the OCI digest and Firecracker artifact version/checksum after publishing those artifacts.
  • Cached immutable artifacts may be reused, but startup never builds infrastructure locally unless an explicit development override is selected.
  • Docker, macOS Container, and Firecracker use the same release identity and fail closed when release metadata is invalid or unavailable.
  • macOS runs the code baked into the pinned image rather than overlaying host source.

Scope

Add a packaged release manifest, a backend-neutral artifact acquisition contract, OCI pull support for Docker and Apple Container, manifest-selected Firecracker artifacts, explicit local-build mode, release-pipeline support, and tests covering pin validation and backend parity. Include gateway artifacts where required to eliminate the adjacent unconditional infrastructure rebuild and keep the Firecracker split infra pair coherent.

This requires a PRD because it changes the release supply chain, package contents, and lifecycle behavior of all three backends.

## Problem Starting a bottle invokes a local orchestrator build on the Docker and macOS Container backends. On macOS, `MacosInfraService.ensure_running()` calls `container build` before it checks the running orchestrator. Docker does the analogous `docker build`. Firecracker instead pulls a verified rootfs artifact, but selects its version from runtime source content rather than a pin assigned when packaging the application. macOS also bind-mounts installed source over the orchestrator image, so merely changing the image reference would not make the packaged artifact authoritative. ## Desired behavior - Every production backend acquires, verifies, and runs an immutable orchestrator artifact selected by the installed application package. - Packaging records the OCI digest and Firecracker artifact version/checksum after publishing those artifacts. - Cached immutable artifacts may be reused, but startup never builds infrastructure locally unless an explicit development override is selected. - Docker, macOS Container, and Firecracker use the same release identity and fail closed when release metadata is invalid or unavailable. - macOS runs the code baked into the pinned image rather than overlaying host source. ## Scope Add a packaged release manifest, a backend-neutral artifact acquisition contract, OCI pull support for Docker and Apple Container, manifest-selected Firecracker artifacts, explicit local-build mode, release-pipeline support, and tests covering pin validation and backend parity. Include gateway artifacts where required to eliminate the adjacent unconditional infrastructure rebuild and keep the Firecracker split infra pair coherent. This requires a PRD because it changes the release supply chain, package contents, and lifecycle behavior of all three backends.
didericis-codex added the Kind/Feature
Priority
High
2
 labels 2026-07-27 11:07:01 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status/Needs Triage
Awaiting initial classification
No Label Kind/Feature
Priority
High
2
Milestone
No items
No Milestone
Assignees
Clear assignees
didericis-claude (didericis (claude)) didericis-codex (didericis (codex)) didericis-gemma (gemma) didericis
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: didericis/bot-bottle#536
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?