ADRs 0164–0166 and issue 190: the container runtime gets a module, a seat and declared settings #271

2026-10-01T22:03:14Z

mesh-admin commented

2026-10-01 22:03:14 +00:00

All three ADRs are proposed. Flip them to accepted once reviewed; the design amendments (05's capability table, 26's seat table) follow in a separate change, since a design may not rest on a proposed record.

0164: a module declares every setting it takes, with a type, a meaning, an optional default and what a change costs (nothing, a reload or a restart). This enforces ADR 0046 / 0112. An undeclared key is refused when set, and every effective value names its source (default, mesh or node).
0165: container-runtime is detected from the kernel, as seat is. "A runtime is running" becomes one probe, shared by the preflight and the runtime module's health. The detector change waits until 0166's seat requirement is enforced, so issue 007 cannot come back.
0166: node-container-runtime is a seat of the mesh's own, held by the docker module. Its verbs and events cover every container on the machine. The holder runs as a supervised process and serves the verbs locally to the host and on the bus to everyone else. The host creates containers through it and never falls back to the command line. The bus is ruled out for the host because the broker itself is a container. Only the host may create or remove a mesh-held container.
Issue 190: the resolver module and the private network both write the runtime's file and declare its service. The collision check never sees the private network's resources, because they are computed.

Checks: records, index, cycle pass.

All three ADRs are **proposed**. Flip them to `accepted` once reviewed; the design amendments (05's capability table, 26's seat table) follow in a separate change, since a design may not rest on a proposed record. - **0164**: a module declares every setting it takes, with a type, a meaning, an optional default and what a change costs (nothing, a reload or a restart). This enforces ADR 0046 / 0112. An undeclared key is refused when set, and every effective value names its source (default, mesh or node). - **0165**: `container-runtime` is detected from the kernel, as `seat` is. "A runtime is running" becomes one probe, shared by the preflight and the runtime module's health. The detector change waits until 0166's seat requirement is enforced, so issue 007 cannot come back. - **0166**: `node-container-runtime` is a seat of the mesh's own, held by the `docker` module. Its verbs and events cover every container on the machine. The holder runs as a supervised process and serves the verbs locally to the host and on the bus to everyone else. The host creates containers through it and never falls back to the command line. The bus is ruled out for the host because the broker itself is a container. Only the host may create or remove a mesh-held container. - **Issue 190**: the resolver module and the private network both write the runtime's file and declare its service. The collision check never sees the private network's resources, because they are computed. Checks: records, index, cycle pass.

mesh-admin added 2 commits 2026-10-01 22:03:14 +00:00

ADRs 0164-0166 and issue 190: the container runtime gets a module, a seat and declared settings f1941304cc

Proposed for the operator's review: settings declared with defaults and cost (0164),
container-runtime as a kernel capability (0165), node-container-runtime seat with the
host creating containers through its holder (0166), and the runtime's file written by
modules that are not its own (190).

Merge remote-tracking branch 'origin/main' into decision/docker-module 3d54fcbb86

jschoubben added 1 commit 2026-10-01 22:48:09 +00:00

Review of 0164-0166 and 190: the mesh's own setting words stay settable; changing runtime verbs are not the console's wildcard; migration steps 1-2 are one push; dnsmasq's dns key dates from 09-23 27c1db8a86

jschoubben added 2 commits 2026-10-02 10:23:29 +00:00

Merge remote-tracking branch 'origin/main' into decision/docker-module 967c793eaa

0164: a setting names the file it lands in (issue 198's leak between one module's files); 190 notes the fourth machine now has the resolver 17ca9a262b

mesh-admin referenced this pull request

2026-10-02 13:19:44 +00:00

Research 018: the operator's machine as modules #291

This pull request has changes conflicting with the target branch.