Cairn
NousResearch/hermes-agent

Docker boot chown repeating despite matching remapped UID ownership

Cluster 35025 · environments. Data as of

Nothing open on GitHub. Fix merged in #35027 on 1 Jun 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #35027. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #35027. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members concern docker/stage2-hook.sh running chown on boot when HERMES_UID/PUID is set to a non-10000 value, even if volume ownership may already match. One is a bug report and two are pull requests that propose skipping the redundant chown; the titles alone don't confirm their status or outcome.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #35027 fix(docker): skip unnecessary boot chown when volume ownership already matches remapped UID

    merged to main

    files: docker/stage2-hook.sh

    Show the diff
    • docker/stage2-hook.sh
      @@ -120,9 +120,7 @@ done
 # mkdir -p block below seeds. Keep them in sync if the seed list changes.
 actual_hermes_uid=$(id -u hermes)
 needs_chown=false
-if [ -n "${HERMES_UID:-}" ] && [ "$HERMES_UID" != "10000" ]; then
-    needs_chown=true
-elif [ "$(stat -c %u "$HERMES_HOME" 2>/dev/null)" != "$actual_hermes_uid" ]; then
+if [ "$(stat -c %u "$HERMES_HOME" 2>/dev/null)" != "$actual_hermes_uid" ]; then
     needs_chown=true
 fi
 if [ "$needs_chown" = true ]; then

1 PR closed without merging

From the close comments: merged via another change 1

  • #35176 fix(docker): skip redundant chown for remapped UID · merged via another change → #35027, #35025
Closed issues · 1
  • Closed#35025[Bug]: `docker/stage2-hook.sh`: `needs_chown` triggers chown on every boot when `HERMES_UID`/`PUID` is set to a non-10000 value, even if volume ownership already matches
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

Subsystem
environments
Merged PRs
#35027
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
1 Jun 2026

For your agent

The same facts, typed.

cluster/35025.json
cluster/35025.md