Audit the remaining repositories for runner egress exposure #788

Open
opened 2026-08-11 23:35:16 +00:00 by coilyco-ops · 0 comments
Member

Four repositories were checked while investigating the pre-commit network
failures: deploy, sirens-echo, agentic-os, infrastructure. Roughly twenty were
not.

Every repository whose CI runs runs-on: docker and fetches from the network
takes the same DinD path. website, eco-app, ward, ward-mcp, cli-guard, atlas,
galaxy-gen, voice-corpus, steam-ops, eco-mods and the rest are unmeasured.

Scope

Per repository, record whether CI fetches from the network, whether it caches,
and whether it opts into the egress proxy. The MTU fix would cover all of them
at once, so this is mainly worth doing to size the problem and to catch
repositories that need neither.

Four repositories were checked while investigating the pre-commit network failures: deploy, sirens-echo, agentic-os, infrastructure. Roughly twenty were not. Every repository whose CI runs `runs-on: docker` and fetches from the network takes the same DinD path. website, eco-app, ward, ward-mcp, cli-guard, atlas, galaxy-gen, voice-corpus, steam-ops, eco-mods and the rest are unmeasured. ## Scope Per repository, record whether CI fetches from the network, whether it caches, and whether it opts into the egress proxy. The MTU fix would cover all of them at once, so this is mainly worth doing to size the problem and to catch repositories that need neither.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/infrastructure#788
No description provided.