You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 11ba67a
Browse filesBrowse the repository at this point in the historyBrowse files
fix(compute): explain root/unresolved USER identity rejection
Creating a sandbox from an image whose OCI USER resolves to root (for
example `USER root`, or a non-root user listed in group 0 via the image's
/etc/group) failed with an opaque, internal-sounding message:
IdentityResolutionFailed: descriptor error: workload identity must not
contain UID or GID zero
It named neither the image nor the offending component, leaked the internal
`descriptor error:` prefix, and offered no remediation.
The Docker and Podman identity resolvers now emit an actionable error before
the identity constructor rejects the zero value. The message names the image,
says which component is zero (user, primary group, or a supplementary group),
where the value came from (the image's USER, its /etc/passwd or /etc/group,
or the policy), and how to proceed (use a non-root image, or set
process.run_as_user and process.run_as_group). A new shared helper,
`root_identity_rejection_message`, keeps the wording consistent across both
drivers and is unit-tested without a Docker/Podman daemon.
This is a diagnostics and documentation change only. Root is still rejected
by `ResolvedWorkloadIdentity::new`, and an image with no USER and no policy
identity still resolves to 1000:1000; no UID/GID mapping, isolation, or trust
behavior is changed.
Also correct `runtimes.mdx`, which claimed images without a USER must set both
policy identity fields; it now matches `default-policy.mdx` and the code (no
USER falls back to UID/GID 1000, and a root USER is rejected unless the policy
sets a non-root identity).
Addresses the error-message and docs acceptance criteria of NVIDIA#4030. The CLI
"print the failure once" criterion is deferred pending maintainer
clarification (elezar) on whether "once" covers the final visible output or
every terminal write including transient spinner frames.
Signed-off-by: Udaya Tejas <[email protected]>
Copy file name to clipboardExpand all lines: docs/how-it-works/sandboxes/runtimes.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -362,7 +362,7 @@ On Docker and Podman, set `process.run_as_user` and `process.run_as_group` in th
362
362
363
363
| Driver | Default identity |
364
364
|---|---|
365
-
| Docker, Podman | The image's `USER`, otherwise `1000`. |
365
+
| Docker, Podman | The image's `USER`, otherwise `1000`. A root `USER` is rejected unless the policy sets a non-root `run_as_user` and `run_as_group`. |
366
366
| Kubernetes | OpenShift SCC namespace annotations, otherwise `1000`. Override with `sandbox_uid` and `sandbox_gid`. |
367
367
| MicroVM | The image's `sandbox` account, otherwise `1000`. Override with `sandbox_uid` and `sandbox_gid`. |
0 commit comments