Repository navigation
Conversation
…ated sandboxes Signed-off-by: Serge Panev <spanev@nvidia.com>
This was referenced Oct 22, 2026
yaoyu-33
marked this pull request as draft
November 18, 2026 01:55
Contributor
|
We’re doing some cleanup of the open PR list. This PR has had no activity for over a month, so I’ve moved it back to draft. If this change is still needed, please resolve any merge conflicts and mark the PR ready for review again when it’s ready to merge. Thanks! |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some world images start their gateway and MCP servers on fixed ports (8000, 8100-8107). Several rollouts on one node then collide in the shared network namespace. Unprivileged Apptainer can give each sandbox its own namespace only with
--net --network none, which also removes the sandbox's route to the model server, and the Stirrup Chat Completions client runs inside the sandbox.This relays the policy traffic through a unix socket, which network namespaces do not affect:
stirrup_runtime.py:serve_unix_to_tcp/serve_tcp_to_unixstream relays and apolicy_endpointcontext. Whenrunner_configcarriesmodel_egress_socket,run_stirrup_rolloutlistens on a loopback port that forwards to the socket and points the client athttp://127.0.0.1:<port>/v1. Any entrypoint that callsrun_stirrup_rolloutgets this without changes.app.py:PolicyEgressRelayopens the host socket and forwards to the model server parsed frommodel_base_url; the socket directory is bound into the sandbox at/egressthroughprovider_options["binds"]; the relay lives exactly as long as the sandbox. New configpolicy_egress_relay: auto | always | never(defaultauto, enabled when the apptainerextra_start_argscontain--netor a--networkoption). Closing cancels in-flight bridges, since the client keeps idle keep-alive connections open.apex_agent_policy_egress_relay, README section, tests for both relay halves, the URL rewrite, detection and spec wiring.Enable per run with
Plain-HTTP model endpoints only. Worlds whose tools need the internet keep the default shared network. Default behaviour is unchanged.