Kit container provisioning: egress session, sandbox network, CA, sentinels, volumes, hooks #239
Notifications
Due Date
No due date set.
Reference: sam/archie#239
Reference in new issue
Block a user
Daemon side of the harness runner: register the egress session under the run credential, create the sandbox network, mount the CA, archie-agent and worktree, set ProxyEnv and SentinelEnv, create volume@1 volumes keyed by execution, run lifecycle@1 hooks, pass the Kit launch argv and agent-sessions verbs to the worker, EnterRuntime before the entrypoint. See docs/prds/external-agent-harness.md (Egress, Container layout).
Close reason
Building blocks landed on main (to
ac738e6d): harness env isolation and uid drop, multi-port relay, kit.Assemble, container.StartKit with hooks/files/volumes and the install-phase boundary; Docker test proves the harness user cannot read the worker's credentials. Task orchestration moved to egkf.6, where profile selection gives it a caller.Imported from beads
archie-core-egkf.9· GitHub #1186 · type task · priority P1 · created 2026-09-25 · closed 2026-09-25