56 lines
2.6 KiB
Markdown
56 lines
2.6 KiB
Markdown
---
|
|
status: active
|
|
initiated: 2026-10-04
|
|
touches:
|
|
- 02-DECISIONS/0165-container-runtime-is-what-a-machine-can-run-and-a-running-runtime-is-its-holders-health.md
|
|
- 02-DECISIONS/0166-the-container-runtime-is-a-node-seat-and-the-host-creates-containers-through-its-holder.md
|
|
- 02-DECISIONS/0203-the-accounts-environment-is-one-modules-and-every-module-contributes-to-it.md
|
|
- 02-DECISIONS/0205-software-the-distribution-does-not-package-ships-as-a-pinned-archive-of-the-module.md
|
|
- 03-DESIGN/01-to-be/37-the-operators-machine.md
|
|
- 03-DESIGN/01-to-be/38-building-the-operators-machine.md
|
|
became: []
|
|
---
|
|
|
|
# 027 — The system layer as modules
|
|
|
|
## What is investigated
|
|
|
|
What runs on the machines below the operator's home and outside the mesh's own services, and which
|
|
of it should be modules. That covers:
|
|
|
|
- the container runtime and its tools;
|
|
- privilege (sudo);
|
|
- the package manager and the software it cannot install;
|
|
- time, locale, the kernel and boot;
|
|
- log rotation;
|
|
- the machine-specific daemons the workstations and servers carry: printing, bluetooth, VPN
|
|
clients, virtualisation, storage, sharing.
|
|
|
|
## Why
|
|
|
|
The operator asked for the system level beside the graphical session. In particular:
|
|
|
|
- a `docker` module (decided in principle by the proposed ADRs 0165 and 0166, never built);
|
|
- a `docker-compose` module for development work, assigned **only to the two workstations**.
|
|
|
|
Measured in [01](01-what-the-machines-run.md): on four machines, almost nothing at this level is
|
|
owned by a module. The pieces differ by machine for no recorded reason. Three findings are security
|
|
matters on their own.
|
|
|
|
## What it touches
|
|
|
|
- **The container runtime seat** (ADRs 0165 and 0166, both proposed).
|
|
- **The host's `package` shape**, which installs from the distribution's official repositories only,
|
|
while the workstations carry 67 and 114 packages from elsewhere.
|
|
- **How a secret reaches the account's environment.** ADR 0203 forbids it in the contributed
|
|
environment, but a predecessor file supplies such secrets today.
|
|
- **The facts the mesh assumes and never declares,** above all that the operator account escalates
|
|
without a prompt.
|
|
|
|
## Documents
|
|
|
|
- [01 — What the machines run](01-what-the-machines-run.md): evidence.
|
|
- [02 — Candidates and questions](02-candidates-and-questions.md)
|
|
- [03 — The account's own tools](03-the-accounts-own-tools.md): `~/.ssh` as one module's, scripts on every machine, the keyring, the laptop's power management, mail as events
|
|
- The predecessor's lessons, shared with research 026: [026/03](../026-the-graphical-session-as-modules/03-what-the-predecessor-taught.md)
|