# NousResearch/hermes-agent · s6-log lock collisions with shared volume across containers

## Open now

- Nothing open on GitHub.

Two bug reports describe s6-log lock collisions in multi-container setups (gateway plus dashboard) that share an /opt/data volume, with one noting the collision loops endlessly. A related pull request titled as a Docker fix proposes a per-container s6-log lock and a logger down marker.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 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.79`: 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

- #34457: \[Bug\]: s6-log lock collision loops endlessly in multi-container gateway + dashboard shared volume setups
- #34480: \[Bug\]: s6-log lock collision in multi-container setup with shared /opt/data volume

## Prior & competing PRs

- **#34473: fix(docker): per-container s6-log lock + logger down marker (#34457, #34480)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `aca11c227`

## Fix status

- No merged fix on record.
- Subsystem: `environments`