# NousResearch/hermes-agent · Docker build context includes .venv directory

## Open now

- Nothing open on GitHub.

Reports and fixes related to the .venv directory being included in the Docker build context, causing issues when building images. Proposed solutions involve adding .venv to .dockerignore or otherwise excluding it.

## 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 #8904. Verify it addresses your case.
- **Recommended:** read PR #8904 (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-8904`. 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

- #8828: \[Bug\]: uv venv already exists when build docker image

## Prior & competing PRs

- **#8904: fix(docker): add .venv to .dockerignore**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `.dockerignore`
- **#8838: fix(docker): exclude .venv from build context**. closed without merge
  - maintainer direction: category `volume_quota`; implication `active`

## Fix status

- Merged to main in PR #8904 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-13`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.