Docker stage2 config migration user context fix

NousResearch/hermes-agent · cluster 118265 · environments

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 2 PRs.

These issues and PRs address a bug where boot-time config migration and Nous reseed in the Docker stage2 startup were not running under the correct user context, causing silent skips for non-root container starts. The proposed fix routes these operations through as_hermes to ensure proper privilege handling.

Open issues1

  • Issue#118265[Bug]: non-root start silently skips the boot-time config migration (stage2 calls s6-setuidgid directly)

Open PRs2

  • PR#118266fix(docker): use as_hermes for config migration and nous reseed in stage2
  • PR#134094Docker: non-root start no longer skips config migration, Nous reseed and dependency refresh (fixes #118265, salvage #118266)

1 PR closed without merging

From the close comments: other 1

  • #118309 fix(docker): route stage2 config migration and Nous reseed through as_hermes · other → #118266, #134094
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
1 PR closed without merging

For your agent

The same facts, typed.