You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Workspace clones run in the golden boot, where Substrate blocks egress #427
What happens: Substrate boots each new ActorTemplate once, as a temporary golden actor in the ate-golden atespace, and snapshots it. The runner prepares workspaces in that boot. A default Substrate install denies all actor egress until the actor has an EgressPolicy. A task policy cannot apply to the golden actor. So every Workspace git clone fails, and the task still reports WorkspaceReady.
In the task, PID 1 (ax-task-runner) started at the template creation time, and /ax/git-error.log shows the failed fetch.
git clone in the
9AEE
task gives gnutls_handshake() failed: The TLS connection was non-properly terminated.
The egress gateway logs egress denied: actor has no egress policy.
Suggested fix: Document the egress requirement. Let AX create or reference an EgressPolicy for the golden boot. Or prepare workspaces on the first boot of the real actor.
Environment: google/ax d0bc38b and Agent Substrate 1d7ca8c, on a local kind cluster (Docker Desktop on Apple Silicon).
Activity
rakyll commentedon Sep 27, 2026
Related to #433.
Skip workspace setup in the golden boot
Skip workspace setup in the golden boot