Note that the Chronicles-AB runner uses host networking

Bridge-network containers on that NAS have no outbound NAT, so the first run failed fetching actions/checkout. The runner and job containers now share the host network. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-15 11:13:31 -04:00
parent ecfb26d40a
commit e50c3a0c1e
2 changed files with 7 additions and 1 deletions
@@ -8,6 +8,10 @@
 # healthcheck. All of that is deploy/aws/deploy.sh, the same script you run from a laptop.
 # The checklist app's "nas" runner on Chronicles-NA is not involved.
 #
+# That runner and its job containers use Docker host networking: containers on bridge
+# networks on Chronicles-AB have no outbound NAT (no DNS, no internet), which made the first
+# run fail while fetching actions/checkout.
+#
 # ONE-TIME SETUP before the first run (see README.md › Deploy to AWS):
 #   1. Make a deploy-only SSH key (e.g. ssh-keygen -t ed25519 -N '' -f deploy_key) and add the
 #      public half to /home/ubuntu/.ssh/authorized_keys on the box.