From f186ea38c868a657ddc541e4cfc1be49e5234c04 Mon Sep 17 00:00:00 2001 From: Oscar Sanderson Date: Fri, 9 Oct 2026 21:18:55 +0800 Subject: [PATCH] chore(conformance): restart the Trust Anchor instead of recreating it run-all.sh recreated conformance-federation-trust-anchor after rewriting its subordinates file, which gives the container a new IP address on the suite network. Nothing has resolved the Trust Anchor by then, so no run is affected today, but a client that had (the suite caches resolved addresses) would keep using the old one. The file is bind-mounted and rewritten in place, so a restart picks it up and keeps the address. Co-Authored-By: Claude Opus 5.5 --- conformance/scripts/run-all.sh | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/conformance/scripts/run-all.sh b/conformance/scripts/run-all.sh index 4f90bb1d..88d57dbb 100755 --- a/conformance/scripts/run-all.sh +++ b/conformance/scripts/run-all.sh @@ -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