Cairn
NousResearch/hermes-agent

Docker credential volume mount conflict fixes

Cluster 82484 · environments. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 1 PR.

These items address a conflict where skill auto-mounting of credential volumes collides with or overrides explicit read-write mounts, particularly affecting OAuth token refresh in Docker sandboxes. The changes aim to prefer explicit volume mount configurations over automatic ones.

Open issues1

  • Issue#82484Docker sandbox: Google OAuth refresh needs a writable token, but skill auto-mount duplicates explicit rw bind as ro

Open PRs1

  • PR#82504fix(docker): let OAuth refresh use explicit writable token mounts

2 PRs closed without merging

From the close comments: closed without comment 1 · duplicate 1

  • #82498 Fix docker credential volume collision · closed without comment
  • #82511 fix(docker): prefer explicit credential volume mounts · duplicate → #82504
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.50: 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

Subsystem
environments
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/82484.json
cluster/82484.md