Cairn
NousResearch/hermes-agent

docker_network setting ignored in backend probe container

Cluster 76906 · environments. Data as of

3 open items. Fix merged in #103660 on 5 Sep 2026. Check it covers your case.

The short answer

0open issues
3open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #103660. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #103660. That is separate from the fix event.
Still open
0 issues and 3 PRs.

A bug where the terminal.docker_network configuration is not honored when launching the backend probe container, causing it to always run with default networking. Multiple fix attempts target this egress control gap.

Open issues0

No open issues.

Open PRs3

  • PR#76911fix(docker): honor docker_network in backend probe (#76906)
  • PR#76926fix(agent): probe container honors docker_network egress control (#76906)
  • PR#90050test(tools): cover container config propagation across sandbox creation

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #103660 fix(tools): backend-probe honours docker_network and execute_code sandboxes keep docker_extra_args/forward_env/env — one container_config shaper for every creator (#76906 #87995 #84027 #100019, salvage #62023)

    merged to main

    files: agent/prompt_builder.py, contributors/emails/[email protected], tests/tools/test_docker_network_config.py, tools/code_execution_tool.py

1 PR closed without merging

From the close comments: duplicate 1

  • #87998 fix(prompt-builder): honor terminal.docker_network in the backend-probe container · duplicate → #87995, #76906, #76911, #76926, #46358
Closed issues · 1
  • Closed#76906prompt_builder ignores terminal.docker_network, so the backend-probe container is always networked
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
environments
Merged PRs
#103660
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
5 Sep 2026

For your agent

The same facts, typed.

cluster/76906.json
cluster/76906.md