Fix s6 user-drop for non-root Docker containers
Cluster 34648 · environments. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue 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
resolved, deciding PR #34837. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug report and two related fixes addressing s6-overlay boot loops when running containers as non-root users, specifically skipping redundant or unsupported privilege-drop steps in that context.
Open issues0
Open PRs0
Fixes on record
-
#34837 fix(docker): boot non-root containers, skip the s6-setuidgid drop when already unprivileged.
files:
docker/cont-init.d/02-reconcile-profiles,docker/main-wrapper.sh,docker/s6-rc.d/dashboard/run,docker/stage2-hook.sh,hermes_cli/service_manager.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#34684 fix(docker): skip redundant s6 user drop · merged via another change →
#34837
Closed issues · 1
- Closed#34648[Bug]: Regression in v0.15.1: non-root Docker + group_add (docker.sock GID) causes s6-overlay boot loop
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.00means 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 LabAt a glance
- Subsystem
- environments
- Merged PRs
- #34837
- Closed issues
- 1
- Attempts
- 1 PR closed without merging