feat(container): add an explicit private worker build network #39
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!39
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/comfy-build-network"
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?
ComfyUI image builds exposed a nested Docker bridge DNS failure: the private worker pod could resolve the same source services, and using that pod network let application CI progress into dependency installation. The shared signed-image builder still used the failing default path.
Adds an explicit
build_network: worker-podopt-in, requiring the private loopback DinD endpoint and no Docker context override. Existing callers retaindefault. The selected mode is included in the signed receipt. The operator must verify a disposable engine per job; a loopback address alone is not proof of isolation. Owner dispatch, protected-branch authorization, scans and the separate signing/publishing job remain required.Validation: seven container tests and seven credential-boundary regressions passed locally, including rejecting unsupported modes/endpoints, preserving default behavior, passing the selected Docker build argument, recording the mode in the receipt, and preventing publication after failed evidence. Workflow YAML/input wiring and
git diff --checkpassed. Commitbd19963daewas fetched read-only and verified as kiyi author and committer, with exact tested contents. All hosted checks passed atbd19963dae: workflow acceptance run 240, repository security run 241, and library tests/integration run 242.Adoption requires a new immutable minor workflow release and a reviewed caller update of both
usesandlibrary_ref; no existing release is changed. The full signed ComfyUI publication still requires acceptance. See adoption and rollback. Related to Comfy-UI issue #1 and application PR #3.