## What this fixes
The docs show Dagger running from many CI systems, but not how to run Dagger itself inside a container, such as a Kubernetes pod, without needing docker socket access or a privileged container. The answer for Kubernetes, Argo Workflows, and Tekton now exists as official guides.
## The fix
Dagger published official guides for this: Dagger on Kubernetes, Dagger with Argo Workflows, and Dagger with Tekton, all linked in the thread by a maintainer. For Kubernetes CI usage these guides are the starting point instead of hand-rolled container nesting.
Source: https://github.com/dagger/dagger/issues/3140
## Why it happens
The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.
## Source
https://github.com/dagger/dagger/issues/3140