Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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
Source: https://github.com/dagger/dagger/issues/3140
Walks through run Dagger inside a container, for example on Kubernetes, step by step.
Shows how to fix authMiddleware builds redirect_url using YOUR_HOST:3000 when NextJS runs inside Docker container. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Explains why GIL contention invisible on a 16-core test VM crushes a 2-core production container.