docs(debugging): add securityContext and /proc/1/root tips for ephemeral containers#3333
Closed
timm13 wants to merge 2 commits into
Closed
docs(debugging): add securityContext and /proc/1/root tips for ephemeral containers#3333timm13 wants to merge 2 commits into
timm13 wants to merge 2 commits into
Conversation
…ral containers Two additions to the Troubleshooting Volume Mounts section, sourced from customer feedback (ticket #8947): - Pods enforcing runAsNonRoot: wolfi-base runs as root by default and will fail with CreateContainerConfigError unless the ephemeral container patch includes a matching securityContext. - Accessing the target container filesystem without volumeMounts: /proc/1/root/ traverses the target container's full mount namespace (overlay + Kubernetes volumes), provided the ephemeral container runs as the same UID. Explicit volumeMounts remain the fallback when security policies block /proc access. Both points verified against a live k3d cluster. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
securityContext required for runAsNonRoot pods:
wolfi-baseruns as root by default. If a pod enforcesrunAsNonRoot: true(without an explicitrunAsUser), adding an ephemeral debug container without a matchingsecurityContextwill fail withCreateContainerConfigError: container has runAsNonRoot and image will run as root. Added a#### Pods enforcing runAsNonRootsubsection with an updated patch example./proc/1/root/ as an alternative to volumeMounts: When
targetContainerNameis set, the ephemeral container shares the PID namespace and can access the target container's full mount namespace via/proc/1/root/<path>— including both overlay filesystem paths and Kubernetes-backed volumes (emptyDir, configMap, PVCs). This requires matching UIDs. Added a#### Accessing the target container's filesystem without volumeMountssubsection explaining when to use this vs. explicit volumeMounts.Both additions sourced from customer feedback (ticket #8947) and verified against a live k3d cluster.
Test plan
runAsNonRoot: true(norunAsUser) and confirmed ephemeralwolfi-basecontainer fails withCreateContainerConfigErrorsecurityContext: {runAsUser: 65532, runAsNonRoot: true}to the patch and confirmed container starts/var/logand file at/tmp(overlay); confirmed both accessible via/proc/1/root/from ephemeral container without volumeMounts/var/login ephemeral container is empty without explicit volumeMounts🤖 Generated with Claude Code