fix(fw,web-arm): pin docker_29 to unblock fleet eval #123
No reviewers
Labels
No labels
bug
enhancement
in-progress
needs-info
needs-triage
p0
ready-for-agent
ready-for-human
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Cloonar/nixos!123
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/docker_29-eval-unblock"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
Two coupled changes that unblock the promtail→alloy migration (#118):
1. docker_29 pin — unblock the eval gate
The 25.11 default docker (
docker-28.5.2) has been EOL/insecure since Nov 2025 and refuses to evaluate, so the pre-commit hook (which dry-builds all hosts on any shared-path change) was red for fw and web-arm. Fixed on the two hosts still on 25.11:devmicroVM — pinvirtualisation.docker.package = pkgs.docker_29(docker comes fromutils/modules/development).sa-core.nix's systemd servicepathfrom a barepkgs.docker(= docker_28, which bypassed the pin) toconfig.virtualisation.docker.package.Each host's 26.05 bump makes these redundant (drop them then).
2. alloy sops scaffold — prep for #118
.sops.yaml: new creation rule forutils/modules/alloy/mirroring promtail's exact recipient set.utils/modules/alloy/secrets.yaml: empty placeholder, to be populated out-of-band.No host imports the alloy module yet, so this part is inert until #121 (PR1).
Follow-up required (manual sops step)
Populate the secret before #121 lands:
add:
alloy-env: LOKI_PASSWORD=<the existing loki password>Verification
Pre-commit hook green for all six hosts (amzebs-01, fw, mail, nas, nb, web-arm).
Related