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
Bind declared ingress forwards at activation on a native Linux host #3646
Follow-up to #3603 (task #3578). That PR binds a box's declared ingress forwards when the box activates on a VM host. On a native Linux host the forward still binds later. Bring the native host to the same behaviour, so that NET-121's activation-time bind holds on every host.
### D3646 — A native Linux host binds a box's declared ingress forwards at activation, before the record goes Active, as a VM host does
kind: task
size: M
est: 220 code, 160 tests
executor: agent
origin: residual
epic: 1437
layers:
- finalize:
- crates/minimald/src/box_actor/setup.rs: In the native (false, _) arm, bind the declared forwards at publish in place of the host_ports_in_use probe, and keep the bound forwarders on the actor
- crates/minimald/src/box_actor/host.rs: Release the forwarders bound at activation when the box stops or is destroyed, also when no attach adopted them
- crates/minimald/src/box_actor/tests.rs: Add a test that a native finalize leaves the declared port bound before the first attach, and keep the held-port refusal tests green
test: cargo test -p minimald a_native_activation_binds_declared_forwards_before_the_first_attach
test: cargo test -p minimald activation_refused_when_declared_port_is_held_by_a_host_program
- net:
- crates/minimald/src/net/policy.rs: Let the publish-time bind run on a native control channel toward a switch address that the daemon draws, and retire host_ports_in_use if no caller stays
- crates/minimald/src/net/gvproxy_network.rs: The first own-IP attach on a native host adopts the forwarders bound at activation and its lease, and does not bind them again
- crates/minimald/src/net/mod.rs: Let finalize draw the box's switch lease early on a native host, so the attach takes the same lease
test: cargo test -p minimald native_attach_adopts_the_forwards_bound_at_activation
proof: On a native Linux host, a program on the host connects to a box's declared ingress port right after min session activate returns, before any attach.
changed nothing: This round changes no code. Both open threads describe tradeoffs that were made on purpose. The replies explain why. The three test lines pass at head 281e69b. To make a switch that cannot start fail
aca7771a
3
pushed
c8cd2ccd
4
pushed
3a4bebda
5
pushed
c1c5385b
test
exit
tail
cargo test -p minimald a_native_activation_binds_declared_forwards_before_the_first_attach
0
running 1 test test box_actor::tests::a_native_activation_binds_declared_forwards_before_the_first_attach ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1550 filtered out; finished in 2.25s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 13 filter
cargo test -p minimald activation_refused_when_declared_port_is_held_by_a_host_program
0
running 1 test test box_actor::tests::activation_refused_when_declared_port_is_held_by_a_host_program ... ok test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1550 filtered out; finished in 2.31s running 0 tests test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 13 filtered o
cargo test -p minimald native_attach_adopts_the_forwards_bound_at_activation
0
running 2 tests test net::gvproxy_network::tests::native_attach_adopts_the_forwards_bound_at_activation_only_from_the_same_switch ... ok test net::gvproxy_network::tests::native_attach_adopts_the_forwards_bound_at_activation ... ok test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 1549 f
That /implement is held, not dropped. The container platform had no instance to give the coder: its pool of prepared containers was full, which happens most just after a deploy. It is asked again every 10 minutes for up to 30.
Nothing to type again: the command gets a rocket when its coder starts, or a refusal that names the reason.
What the platform said
could not start the coder: Error: there is no container instance that can be provided to this durable object
Activity
fix(minimald): keep declared forwards host-held on a VM host
docs(specs): name the NET-121 residuals in the activation bind note
norrietaylor commentedon Nov 20, 2026
Task
Source: #3646
Plan block
norrietaylor commentedon Nov 20, 2026
/implement
minimal-foundry commentedon Nov 20, 2026
Pull request #3703 is open as a draft for D3646.
branch
agent/3646-a-native-linux-host-binds-a-box-s-declared-ingre· epic #143756427a1eaca7771ac8cd2ccd3a4bebdac1c5385bcargo test -p minimald a_native_activation_binds_declared_forwards_before_the_first_attachcargo test -p minimald activation_refused_when_declared_port_is_held_by_a_host_programcargo test -p minimald native_attach_adopts_the_forwards_bound_at_activationVerify
min task run agent-verify: exit 0Outside the task's
layers:, so the PR is a draft:crates/minimald/src/net/provider.rsdocs/specs/18-spec-box-networking/18-spec-box-networking.mdUpdated 2026-11-21T06:03:53.784Z.
minimal-foundry commentedon Nov 20, 2026
That
/implementis held, not dropped. The container platform had no instance to give the coder: its pool of prepared containers was full, which happens most just after a deploy. It is asked again every 10 minutes for up to 30.Nothing to type again: the command gets a rocket when its coder starts, or a refusal that names the reason.
What the platform said
could not start the coder: Error: there is no container instance that can be provided to this durable object
docs(specs): cite #3689 for the VM-backed NET-121 residuals