You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Milestone: Containerized development for the flyingrobots Rust repositories #1
.dag: issue-dag/2.id: flyingrobots/devcontainers#1.kind: container.children: [flyingrobots/devcontainers#2, flyingrobots/devcontainers#3, flyingrobots/devcontainers#5, flyingrobots/devcontainers#4, flyingrobots/geordi#151, flyingrobots/bunny#207, flyingrobots/echo#971, flyingrobots/ninelives#6, flyingrobots/ninelives#7, flyingrobots/bunny#208]source: Maintainer rule of 2026-11-08: no builds on the host; use dev containers
Milestone
This is a container card. Do not open a pull request for it.
Work its children in dependency order. Start with a child that has no open blockers.
Close this card when every child is closed.
1. Background Context
On 2026-11-08 the maintainer ruled that builds, tests, and toolchains must not run on the host. They run in development containers. The rules for Docker resources are in docs/hygiene.md of flyingrobots/devcontainers.
2. Goal
Each Rust repository (Geordi, Bunny, Echo, ninelives) builds and tests through one guarded runner and one shared base image, without Docker litter.
2b. Exit criteria
The base image and the runner exist and pass their tests.
Each repository has a dev container definition and a wrapper that calls the runner.
The two blocked fixes (the ninelives tokio patch and the Bunny lockfile update) are done through the runner.
3. Prerequisites
None.
4. Scope
In:
The base image, the runner, per-repository wrappers, and the two blocked fixes.
Activity