Repository navigation
validator: a containerised validator joins the networks it creates - #177
Merged
Merged
Conversation
…work it creates, so it reaches its sibling containers
…a small card gives the SLM 0.72 so it fits beside the probe agent
… it 0.68, so the sampler warmup fits
… the image installs without resolving
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.
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.
/.dockerenv, orMT_SELF_CONTAINER),create_networkconnects the validator's own container to the new network andremove_networkdisconnects it first.🤖 Generated with Claude Code