Skip to content

Milestone: Containerized development for the flyingrobots Rust repositories #1

Open

Description

@flyingrobots
.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.

Out:

  • GPU containers. Windows hosts.

5. Why now

Open pull requests (flyingrobots/geordi#76, flyingrobots/bunny#206) need local validation that is not allowed on the host.

6. Risks

A runner bug can leave litter. The audit in the runner card catches it.

7. Definition of Done

Every child is closed.

8. Stakeholders

  • James Ross (maintainer): owns the repositories and the host.

9. Related Issues

None.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions