Repository navigation
TOOLS-139: qualify Docker protocols and lifecycle in CI - #169
Merged
averycrespi merged 17 commits intoOct 13, 2026
Merged
averycrespi merged 17 commits into
averycrespi merged 17 commits into
Conversation
Exercise the deployed binary through disposable protocol, trust and lifecycle fixtures before accepting the stacked revision. Keep real container evidence blocking in CI without weakening product address or custody policy.
Internal-only Docker bridges do not publish ports. Preserve their egress isolation and end-to-end TLS with bounded owned loopback TCP relays rather than weakening fixture network policy.
Expose only fixed startup failure categories so container-only failures can be diagnosed without publishing private runtime output or weakening fixture restrictions.
Keep the empty capability set and read-only image by executing verified identical bytes from bounded private tmpfs rather than inheriting the upstream inode capability requirement.
Keep nondefault public-origin authority intact in the optional operator example and its container qualification fixture rather than forwarding only the hostname.
Assert the existing stricter Host-before-Origin boundary for internal aliases rather than expecting the later public-origin validation status.
The preceding commit used an incorrect command-only hook path, so its pre-commit hook was ignored. Validate its exact diff with configured lint-staged tasks, then run the normal configured pre-commit hook for this bookkeeping commit. No source bytes changed; no history was rewritten.
averycrespi
marked this pull request as ready for review
October 13, 2026 10:42
averycrespi
added this pull request to stack #170
October 13, 2026 19:06
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.
Context
TOOLS-139 qualifies Gateway's Docker deployment across protocols and lifecycle boundaries. Stacked on #168 (
avery/tools-138-docker-packaging), notmain.Changes
Review Notes
Independent source reviews are complete; the final audit-admission review found no material issues. Qualification is bound to head
72b125e46e97b395d633d084866b3181bd5795b8, base976d3244006b23e3e6a8a899fdaee8ac82fc5f21, and tested merge checkoutf78af0cc76ac0f960e1f7adbf2fce81aa80c8b51.The actual Docker report passes all 13 cases, packaging and cleanup. Earlier failed runs remain historical failures; the observed audit refusal does not identify their competing writer or establish every historical cause.
Commit
4a793a72inadvertently selected the wrong hook directory. Before publication, all ten changed files passed the configured lint-staged tasks without byte changes, and72b125e4ran the normal pre-commit/lint hook as an empty bookkeeping commit. No history was rewritten.No local Docker execution, registry publication, merge or deployment. Evidence is Linux/amd64 container qualification, not live Debian/provider/installed-proxy adoption, other architectures or physical power-loss durability.
Test Plan
85a96a9c577e78cef80f89937141b9ee43c8052d31a57b98ccfff4762b49dd2c. Shipped imagesha256:b60574b5c61e5cf1eb9269a90af1e4327258980e314c58a7863215ff09ad5b57.TestProxyIPv6SocketFallback, 187 frontend Node tests (zero skipped), frontend typecheck,make fmt-check, and 31 browser tests.make test-ci(79 tests), Gatewayverify,test-unit,test-harness; race-enabled catalog/contract and storage-fault tests; four native lifecycle/no-replay regressions; formatting, 69 relative documentation links and full cumulative patch/history secret scans.