NousResearch/hermes-agent

Docker build context broken symlink exclusion

Cluster 13925. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #13926 fix(docker): exclude runtime data/ from build context · merged via another change
  • #13940 fix(docker): exclude data/ from build context to prevent broken-symlink build failures · done elsewhere → 85caa5d, #13926, #13925
Closed issues · 1
  • Closed#13925[Bug]: docker compose build fails with 'invalid file request' when container writes broken symlinks to bind-mounted /opt/data
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.67: 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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.