0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-11 21:26:44 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 5aa7506e36 fix(swarm-lab): drop bind-dynamic so the manager keeps its IPv4 resolvers

dnsmasq 2.93 with bind-dynamic enumerates IPv6 before IPv4 (network.c:836-875). A veth that disappears between the RTM_GETADDR snapshot and the SIOCGIFFLAGS ioctl makes that pass return 0, which skips the IPv4 pass entirely while the interface-record collector still runs and releases every listener not marked found. The v6 addresses already dumped survive; the whole IPv4 set does not. Recovery would come from the next netlink address event, so the loss becomes permanent when the churn stops on a release.

That is what killed web-app-matrix 0: the manager kept only [::1]:53 and eight fe80 link-locals while ip -4 addr still showed all four addresses, so ghcr.io stopped resolving and the image pull failed ten times. Both workers, same image and same config, held the complete set on the same fds. daemon.json points container DNS at 172.17.0.1, so every container on that node lost resolution at the same instant.

Reproduced on the same dnsmasq version: 889 full IPv4 release/recreate cycles under a veth storm, with ::1 never released once; the same storm without bind-dynamic produced no listener events at all. Without the directive dnsmasq binds one wildcard pair and reads the arrival interface from IP_PKTINFO, and wildcard listeners carry iface == NULL, which the collector skips outright.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-02 14:04:13 +02:00

coredns

refactor(env): move env/default.env to repo-root default.env and drop env/

2026-05-21 16:22:33 +02:00

package-cache

fix(svc-runner): fix piop same root issue as apt

2026-06-24 18:31:14 +02:00

package-cache-frontend

Merge remote-tracking branch 'upstream/main' into feature/self-host-runners

2026-06-27 23:45:38 +02:00

registry-cache

…

swarm

fix(swarm-lab): drop bind-dynamic so the manager keeps its IPv4 resolvers

2026-08-02 14:04:13 +02:00

.gitignore

…

cache.override.yml

refactor(structure): nest prefix-grouped sibling files into subfolders

2026-07-14 20:00:03 +02:00

cache.shared.override.yml

feat(worktree): isolated per-branch checkouts sharing one cache stack

2026-07-28 16:15:59 +02:00

noports.override.yml

fix(svc-runner): publish no dev-stack ports in nested DooD deploys

2026-07-10 18:43:34 +02:00

README.md

…

worktree.override.yml

feat(worktree): isolated per-branch checkouts sharing one cache stack

2026-07-28 16:15:59 +02:00

README.md

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/ or tests/.

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.