Repository navigation
ci: boot the SOC stack's MSI server under its hardening (#1068) - #1074
Merged
Merged
Conversation
#1071's first deploy on odin crash-looped ('exec caddy failed: Operation not permitted'): the image's caddy binary carries cap_net_bind_service as a file capability, and the compose had dropped every capability. Nothing in CI started the container, so odin was the first place it showed. The hardened-boot job now boots soc/caddy like the sensitive tier's five, with stacks/soc/compose.yaml in the proof cache's key. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🟢 Approval recommended
The new check correctly exercises the intended service and invalidates its proof when relevant compose inputs change.
0 open findings
What changed in this PR
Adds CI coverage to ensure the SOC MSI server boots successfully under its production hardening.
Changes:
- Adds SOC Caddy compose inputs to the boot-proof cache key.
- Boots and health-checks the hardened SOC Caddy service in CI.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Adds cached hardened-boot validation for the SOC MSI server. |
🧠 Review effort: Balanced
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows #1072.
Why
#1071's first deploy on odin crash-looped:
The image's
caddybinary carriescap_net_bind_serviceas a file capability, and the compose had dropped every capability. #1072 fixed it. But nothing in CI starts that container: the Boot hardened services job only boots the sensitive tier's five, so odin was the first place the fault showed.What
check_hardened_boot.sh --stack soc --service caddy, the same check as the sensitive tier's five. It boots the one service from the realcompose.yamlon an internal network, waits for its own healthcheck, then readsdocker inspectto confirm the container really ran read-only, withCapDrop=ALLandno-new-privileges.stacks/soc/compose.yaml. The proof itself is keyed on the service's resolved config (digest, user, caps) and the script, so a Caddy bump, or acap_addtidied away, boots again.check_caddyfile.sh); this step proves the container starts.Checked
yamllintpasses onci.yml, andseed-validation-env.shseeds the soc stack's env. There is no docker where this was written, so this PR's own Boot hardened services run is the first boot. No proof is cached forsoc/caddyyet, so it boots for real rather than passing from cache.🤖 Generated with Claude Code