Finding / heypi

2026-10-13-heypi-docker-uses-normal-bridge-networking-without-a-heypi-egress-selector

Docker uses normal bridge networking without a heypi egress selector. This corrects a historical network-off assumption. The current Docker runtime runs a detached container with workspace/shared binds, a read-only skills bind and runtime environment values, but no network selector, user override, capability drops or resource limits. Normal Docker defaults attach it to the bridge and use masquerading for external access. Effective connectivity remains subject to daemon, routing and firewall policy. The template forwards GITHUB_TOKEN into runtime environment only when the operator supplies it.

Channel: preview-or-beta heypi 0.3.0-beta.2. Half: defect. Date: 2026-07-21 (historical beta.0 rewrite); re-verified for the 2026-10-13 profile.

Operator consequence: Do not transfer the old Docker network-none default to the 0.3 beta. Enforce egress policy at the daemon/firewall or in a custom runtime and test the routes that matter. Inspect runtime environment values for credentials visible to model-directed commands. The docker() builder itself exposes only workspace, image and env; neither approvals nor the container label establish a network boundary.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-heypi-docker-uses-normal-bridge-networking-without-a-heypi-egress-selector

Profile citations

  • heypi / claim / docker-default-bridge-no-egress-selector
  • heypi / posture / governance

Source links

Primary links, including exact changelog lines when available.