fix(ci): run dashboard health probes inside container - #342
Merged
Conversation
Signed-off-by: TH3478 <1934154460@qq.com>
Signed-off-by: TH3478 <1934154460@qq.com>
This was referenced Sep 5, 2026
Quchaosheng
approved these changes
Sep 6, 2026
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.
Summary
localtrust mode instead of trusting the Docker bridge network.Root cause
The
container-full-stackworkflow published the dashboard on127.0.0.1:8080and then probed it from the GitHub Actions host. Docker port forwarding presents that request to the backend as the bridge gateway (for example,172.18.0.1), so the backend correctly rejected it with403 untrusted_clientunder the defaultlocaltrust policy.The workflow now probes
127.0.0.1:8080throughdocker compose exec, matching the dashboard's existing container health-check path without weakening the inbound HTTP trust boundary.Validation
python3 -m pytest tests/unit/test_container_baseline.py tests/unit/test_container_profiles.py -q— 34 passeddocker compose config --quiet— passedgit diff --check— passedThe local environment does not provide Ruff or actionlint; the corresponding GitHub checks will validate them remotely.
Hosted validation on commit
56e6f58passed all 10 reported checks. Thestatic-and-cpu-imagejob completed the image build, CPU smoke, in-container dashboard health/readiness probes, container contract checks, SBOM generation, and vulnerability scan successfully.Scope
This PR changes only the container CI workflow, its regression test, and the focused Task Packet authorizing those paths. It does not change the backend trust policy, Compose security settings, application behavior, or the Issue #168 implementation.
Related to #340.