7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	363039f337	mesh-build-image README: a node without tun is healthy and not eligible, as the module now says (issue 1126)	2026-10-28 15:01:42 +01:00
jschoubben	d13f74df40	A node that cannot open /dev/net/tun takes no image build, and every node loads tun at boot and keeps its running kernel's modules ... An image build node up 24 days had lost its running kernel's modules to a linux-lts upgrade, so tun could not load and every RUN line failed in pasta. mesh-build-image now proves the tun device and, whatever its look refuses, judges its node not eligible (capacity 0 with the reason), so the asks go to a node that can build them. The kernel module loads tun at boot and declares kernel-modules-hook, which keeps the running kernel's modules across an upgrade. Needs mesh-sdk fix/ace-tun (Puller.Eligible).	2026-10-28 12:44:58 +01:00
jschoubben	dcf32576a8	mesh-build-image: build with the module's directory as context, so a Dockerfile in a subdirectory finds its COPY paths (issue 1703) ... photos' admin-client, client and server Dockerfiles live in subdirectories and copy paths from the module's root (admin-client/..., client-server/serve.mjs), as build-agent built them and as the fingerprint reads the module's whole directory. Taking the Dockerfile's own directory as context failed every such COPY with copier: stat "/admin-client/package.json": no such file or directory, on shanks and on ace. Quick fix (rejected): move photos' Dockerfiles to its repository root; it changes the operator's photo application and leaves the trap for the next module. Thorough fix (chosen): one context for every image, the module's directory; it never leaves that directory, so the isolation of ADR 0487 section 2 holds.	2026-10-26 21:25:24 +01:00
jschoubben	3ca48ff230	Refuse build steps under a free-space floor and release workspaces, so the build modules stop filling a build node's disk (issue 1839) ... mesh-build-go, mesh-build-node and mesh-build-image refuse every fetch, test and build, and say unhealthy, while their work or cache filesystem has less than 20 GiB free (build-agent's floor), so the builder chooses another node instead of filling this one. Each serves build_<x>_release, removing a workspace once its caller's last step answered; a failed fetch removes its own; a workspace never released goes two hours after its last use (ADR 0509) in place of a day, never while a step holds it. Pins mesh-sdk's fix/1839-build-floor (buildstep.Floor, buildstep.Workspaces).	2026-10-23 12:17:58 +02:00
jschoubben	72effa1fb1	Copy an upstream artifact into the artifact store by its pinned digest (issue 1587, S11-S13, ADR 0498 §4)	2026-10-22 17:57:05 +02:00
jschoubben	9e2d1164f0	Give mesh-build-image the registry's address as the seat's reach, which the provisioner's client fills (issue 1703)	2026-10-22 11:07:50 +02:00
jschoubben	692fc3e1ab	Add mesh-build-image: rootless image builds with buildah, pushed by tag from trunk only (issue 1703)	2026-10-22 10:27:01 +02:00