Skip to content

docs(rfc): rootless-Docker spike — analysis + validation plan (#1176) - #373

Merged
LukasWodka merged 1 commit into
developfrom
spike/lpi-rootless-validation
Jul 23, 2026
Merged

docs(rfc): rootless-Docker spike — analysis + validation plan (#1176)#373
LukasWodka merged 1 commit into
developfrom
spike/lpi-rootless-validation

Conversation

@LukasWodka

@LukasWodkaLukasWodka commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

What

The spike deliverable for the rootless-Docker-primary decision (Asad's review of RFC 0001). A design + analysis doc plus the validation plan that gates Tier 1 (#1177):

  • Kernel prerequisite coverage by distro (cgroup v2 + unprivileged userns) — mainstream targets (Ubuntu/Debian/RHEL 9/SUSE) are default-on; old/hardened kernels fall to Tier 2.
  • Rootless install mechanicsdockerd-rootless-setuptool.sh, the subuid/subgid precondition (the one residual named privileged touch), systemd --user + a nohup fallback for HPC nodes.
  • k3d on the rootless socket — cgroup delegation, modprobe-free networking, port <1024.
  • The perf risk — fuse-overlayfs vs native overlay for the push (dataset-copy) path, with a measurement plan.
  • Validation plan (§5) — the experiments to run on real hosts, including a hardened/userns-disabled node to exercise the honest Tier-2 fall-through.
  • Preliminary go/no-go — provisional GO, with three blocking unknowns for #1177 (fuse-overlayfs push perf, cgroup delegation, HPC user-systemd).

Note

The §5 experiments require real target hosts / CI runners — they can't run from a dev laptop, so this doc is analysis + plan + preliminary verdict, not the executed measurements. It gates #1177 (Tier 1); it does not block #1172 (routing) or #1175 (Tier 0).

Part of the least-privilege install epic (#1168). Part of tracebloc/backend#1176 (leaves the ticket open for the real-host experiments).

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only; no runtime, auth, or data-path code changes.

Overview
Adds docs/rfcs/0001-rootless-spike.md, the spike deliverable for using rootless Docker as the k3d backend under the least-privilege install RFC. It frames what must hold before Tier 1 (#1177) ships: kernel probes (cgroup v2 + unprivileged userns), distro tier expectations, rootless install mechanics (subuid/subgid, systemd --user / HPC fallback), and k3d-specific checks (cgroup delegation, networking, ports).

The doc calls out fuse-overlayfs vs native overlay as the main UX risk for dataset push/ingest, defines a §5 real-host experiment matrix (probe accuracy through Tier-2 fall-through on hardened nodes), and records a provisional GO with three blocking unknowns for #1177. It explicitly does not block routing (#1172) or Tier 0 (#1175).

Reviewed by Cursor Bugbot for commit 8560f56. Bugbot is set up for automated code reviews on this repo. Configure here.

…nary go/no-go (#1176)
Deliverable for the rootless-primary spike: kernel-prerequisite coverage by
distro, rootless install mechanics (subuid/subgid + systemd --user), k3d-on-
rootless-socket caveats (cgroup delegation), the fuse-overlayfs push-perf risk,
a concrete validation plan for real hosts (incl. a hardened/userns-disabled node
to exercise the Tier-2 fall-through), and a provisional GO conditioned on those
experiments. The §5 experiments need real target hosts and gate #1177 (Tier 1);
nothing here blocks #1172 (routing) or #1175 (Tier 0).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@divyasinghdsdivyasinghds left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve (doc). Honest, well-scoped spike. Note: the §5 validation experiments (fuse-overlayfs push perf, k3s cgroup delegation under systemd --user, HPC no-user-systemd) remain a gate on #1177 itself — please track them there.

@LukasWodka
LukasWodka merged commit 99dca47 into developJul 23, 2026
9 checks passed
@LukasWodka

Copy link
Copy Markdown
ContributorAuthor

Functional review \u2014 passed\n\nThis PR is documentation only (an RFC write-up plus its validation plan) \u2014 there is no runtime behaviour on dev to exercise, so functional review on the dev environment is not applicable. passed at merge. Advancing on that basis.

@LukasWodka
LukasWodka deleted the spike/lpi-rootless-validation branch August 14, 2026 13:53
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@LukasWodka@divyasinghds@saadqbal@waqaskhanroghani@shujaatTracebloc