# NousResearch/hermes-agent · docker_network setting ignored in backend probe container

## Open now

- 0 issues, 3 PRs open on GitHub.
- PR #76911: fix(docker): honor docker_network in backend probe (#76906)
- PR #76926: fix(agent): probe container honors docker_network egress control (#76906)
- PR #90050: test(tools): cover container config propagation across sandbox creation

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.

## TL;DR

- 6 member(s): 0 open issue(s), 1 closed issue(s), 3 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #103660. Verify it addresses your case.
- **Recommended:** read PR #103660 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-103660`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.33`: the share of member 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.

## Closed / duplicate issues

- #76906: prompt_builder ignores terminal.docker_network, so the backend-probe container is always networked

## Prior & competing PRs

- **#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 · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/prompt_builder.py`, `contributors/emails/301893261+sagitario-jpn@users.noreply.github.com`, `tests/tools/test_docker_network_config.py`, `tools/code_execution_tool.py`
- **#76911: fix(docker): honor docker_network in backend probe (#76906)**. open
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `74bd43cd1215`, `#76906`, `#46358`, `#62023`, `#76911`, `#76926`, `#59149`, `#374151`
  - files: `agent/prompt_builder.py`
- **#76926: fix(agent): probe container honors docker_network egress control (#76906)**. open
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `7ff9a33414e1`, `#46358`, `#62023`, `#76911`, `#76926`, `#59149`, `#76906`, `#374151`
  - files: `agent/prompt_builder.py`, `tests/agent/test_prompt_builder.py`
- **#87998: fix(prompt-builder): honor terminal.docker_network in the backend-probe container**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#87995`, `#76906`, `#76911`, `#76926`, `#46358`
- **#90050: test(tools): cover container config propagation across sandbox creation**. open
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#60815`, `#103660`
  - files: `tests/tools/test_docker_network_config.py`, `tests/tools/test_file_tools_container_config.py`

## Fix status

- Merged to main in PR #103660 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-05`.
- Subsystem: `environments`