Skip to content

CI: no workflow builds or boots the servers' Docker images #5598

Open

Description

@cliffhall

Problem

No workflow builds the seven servers' Docker images. Nothing under .github/workflows/ runs docker build, so a Dockerfile change reaches main and a release with no check that the image still builds, boots, or stops cleanly.

The v2.5.0 release shows the gap (release issue #5572): src/memory/Dockerfile gained STOPSIGNAL SIGINT (#5485), which decides whether docker stop lets the server remove its lock file, and src/git/Dockerfile and src/fetch/Dockerfile changed too (#5483). The release verification built and exercised those images by hand, because nothing else would have.

The pre-push gate does not build images either, and the rule is that a check added to CI is added to local:gate:stages in the same change (AGENTS.md, Before pushing), so this is a decision about both.

To decide

  • Whether CI builds each image a PR changes (or all seven), and boots it with a tools/list over stdio.
  • Whether the memory image's docker stop behavior (the lock removed, the container stopped before the timeout) is asserted there.
  • Whether the same check joins local:gate, where it needs a Docker daemon, or stays CI-only with that exception recorded.

Expected

A Dockerfile change that breaks the image fails a check before it merges.

Activity

  1. added this to the v2.6.0 milestone on Nov 18, 2026
  2. added
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Nov 18, 2026
  3. self-assigned this
    on Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changev2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions