mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
70f27f82ef
The LUKS step of the DR drill died on `The file /dev/mapper/usbdrill does not exist and no size was specified.` -- from mkfs, not from cryptsetup, because luksOpen had exited 0. The node did have a udev, and it had created the mapper entry: as a symlink to ../dm-1. Modern udev no longer mknods, it only manages symlinks, and the /dev/dm-N target it points at is a devtmpfs node that a container's tmpfs /dev never receives. Without a udev libdevmapper creates the node itself, which is why the debian nodes passed -- their image ships no udevd at all, while arch cannot install systemd without one. Masking udevd in the node image removes the whole class rather than one call site. DM_DISABLE_UDEV rides on the node containers instead of the script because the drill opens the volume a second time through the recover CLI in a separate docker exec, which would not inherit an export. The block-device check then fails loudly with both prerequisites named, and closes the mapping first so an abort cannot leak it onto the runner -- device-mapper is not namespaced and every distro round shares the VM. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Compose Configuration 🧩
This directory holds the static configuration assets consumed by the top-level compose.yml of the local development and CI testing stack.
Scope 📋
- The directory MUST contain only files that are bind-mounted into a
service defined in
compose.yml. - The directory MUST NOT host application configuration that belongs to
an Ansible role. Per-role compose payloads live under
roles/<role>/templates/. - The directory MUST NOT host workflow scripts, test fixtures, or
build helpers. Those belong under
scripts/ortests/.
Layout 🗂️
Each compose service that needs static configuration owns a
sub-directory whose name matches the service. New service-specific
config MUST go into the matching sub-directory rather than at the
compose/ root.
For the rules that govern compose.yml itself (env-variable contract,
profile gating, resource caps), see
compose.yml.md.