# NousResearch/hermes-agent · Docker build context broken symlink exclusion

## Open now

- Nothing open on GitHub.

A bug report and related fixes addressing Docker build failures caused by broken symlinks in bind-mounted data directories being included in the build context. The proposed solution involves excluding the runtime data directory from the build context.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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

- #13925: \[Bug\]: docker compose build fails with 'invalid file request' when container writes broken symlinks to bind-mounted /opt/data

## Prior & competing PRs

- **#13926: fix(docker): exclude runtime data/ from build context**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`
- **#13940: fix(docker): exclude data/ from build context to prevent broken-symlink build failures**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `85caa5d447edecab62f6a16b07c6869987a426fe`, `#13926`, `#13925`

## Fix status

- No merged fix on record.