You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Home Assistant's hardened boot was proved once; nothing re-runs it when Dependabot moves the digest #534
stacks/sensitive/README.md on Home Assistant's hardened configuration — read-only root, every capability dropped, two tmpfs mounts: "That was one boot of one digest. Dependabot moves the digest monthly; nothing here re-runs the boot."
The proof that the container starts and stays healthy under that configuration was taken once, on the monitoring host, against a digest that has since been bumped twice (#465, and the 2026.9 line). CI validates the compose file's shape; it does not start the container. So every merged bump silently re-opens the question the hardening answered, and the first time the answer is "no" will be on trinity, after the deploy.
The same is true in principle of every service in the tier; Home Assistant is the one the README calls out because it has the most surface (an integration loader that writes where it likes) and the tightest configuration.
Options
A scratch-compose boot in CI on the changed service, --wait with the healthcheck, then down -v — the mechanism scratch-compose-boot already describes for measuring images, pointed at Dependabot PRs.
A make smoke STACK=sensitive target run by hand before merging a bump, written into the Dependabot PR checklist.
Accept it, and say so in the README in place of the sentence above.
Done when
A digest bump to Home Assistant either boots the hardened container somewhere before it merges, or the README records the decision not to.
scripts/check_hardened_boot.sh runs in a new CI job, Boot hardened services. It boots Home Assistant from the real compose.yaml on an internal-only network and waits for its healthcheck. Then it reads the hardening back with docker inspect, so a softened compose.yaml fails the job instead of passing it. The job runs on every change to the service's resolved config, its config directory or the script. Its proof is cached the way #625 caches --probe's.
The job has passed on the PR's four runs and on the push to main after the merge (16:41 UTC). So a Dependabot digest bump to Home Assistant now boots the hardened container in CI before it can merge, which is the first half of "Done when". make check-hardened-boot runs the same check by hand.
Activity
Merge pull request #646 from Gerrrt/gerrrt/ha-hardened-boot-534
Gerrrt commentedon Sep 23, 2026
Done by #646, merged 2026-09-23 16:41 UTC.
scripts/check_hardened_boot.shruns in a new CI job, Boot hardened services. It boots Home Assistant from the realcompose.yamlon an internal-only network and waits for its healthcheck. Then it reads the hardening back withdocker inspect, so a softenedcompose.yamlfails the job instead of passing it. The job runs on every change to the service's resolved config, its config directory or the script. Its proof is cached the way #625 caches--probe's.The job has passed on the PR's four runs and on the push to main after the merge (16:41 UTC). So a Dependabot digest bump to Home Assistant now boots the hardened container in CI before it can merge, which is the first half of "Done when".
make check-hardened-bootruns the same check by hand.