Skip to content

chore(conformance): restart the Trust Anchor instead of recreating it #623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
osanderson merged 1 commit into from
Oct 9, 2026
Merged

chore(conformance): restart the Trust Anchor instead of recreating it #623

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion conformance/scripts/run-all.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -574,7 +574,13 @@ with open(path, "w") as f:
f.write("\n")
' "$subordinates" "$as_jwks"

(cd "$SERVER_DIR" && docker compose up -d --force-recreate conformance-federation-trust-anchor) >>"$WORKDIR/docker-compose-federation.log" 2>&1
# Restart rather than recreate: the subordinates file is bind-mounted
# and was just rewritten in place, so restarting the same container
# picks it up while keeping its IP address on the suite network.
# Recreating it would give it a new IP, which breaks anything that
# already resolved conformance-federation-trust-anchor (the suite
# caches resolved addresses), should the order here ever change.
(cd "$SERVER_DIR" && docker compose restart conformance-federation-trust-anchor) >>"$WORKDIR/docker-compose-federation.log" 2>&1
wait_federation_ready 18457 conformance-federation-trust-anchor

local ta_jwks
Expand Down
Loading