Skip to content

validator: a containerised validator joins the networks it creates - #177

Merged
BANADDA merged 4 commits into
mainfrom
sibling-networks
Oct 28, 2026
Merged

BANADDA merged 4 commits into
mainfrom
sibling-networks

Conversation

@BANADDA

@BANADDA BANADDA commented Oct 28, 2026

Copy link
Copy Markdown
Member

The validator runs in its own container on the compose network, while the probe agent, SLM, gateway and miner containers each sit on a private network the validator created. It could not reach any of them, so the probe agent never became ready on the GPU box.

  • When the validator runs inside a container (/.dockerenv, or MT_SELF_CONTAINER), create_network connects the validator's own container to the new network and remove_network disconnects it first.
  • The gateway's upstream is the validator's address on the sandbox network when it has one, so services listen on all interfaces inside the container. Outside a container nothing changes.

🤖 Generated with Claude Code

…work it creates, so it reaches its sibling containers
…a small card gives the SLM 0.72 so it fits beside the probe agent
@BANADDA
BANADDA merged commit ef476ac into main Oct 28, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant