# NousResearch/hermes-agent · Docker container reuse ignores image and mounts config

## Open now

- Nothing open on GitHub.

A bug where cross-process container reuse does not account for image or mount differences, and related fixes that scope Docker reuse to immutable configuration properties.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #131895. Verify it addresses your case.
- **Recommended:** read PR #131895 (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-131895`. 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.67`: 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

- #79816: \[Bug\]: cross-process container reuse ignores image and mounts, with no warning when they differ

## Prior & competing PRs

- **#131895: fix(tools): scope Docker reuse to immutable config \[risk 0.30\]**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_docker_environment.py`, `tools/environments/docker.py`, `website/docs/user-guide/configuration.md`
- **#79832: fix(tools): scope Docker reuse to immutable config**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#131895`

## Fix status

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