Docker in Docker runs nested containers inside a privileged runner pod and can use the Docker daemon to build images. ARC Kubernetes mode does not require privileged mode and spins up separate pods for workload containers. The security trade off is clear: Docker in Docker offers daemon based flexibility, while Kubernetes mode reduces host access risk.
Why Docker in Docker and ARC Kubernetes Mode Are Different Operating Models
Docker in Docker and ARC Kubernetes mode solve similar runner orchestration problems, but they do it with very different trust boundaries. Docker in Docker nests container execution inside a privileged runner pod, which means the Docker daemon becomes part of the build path. ARC Kubernetes mode keeps the runner unprivileged and launches separate pods for workload containers, shifting risk away from host-level Docker access.
The practical difference is not just where containers run, but what kind of control the runner needs over the underlying system. In Docker in Docker, the runner can build images through the daemon and therefore needs stronger host access assumptions. In Kubernetes mode, the runner delegates execution to Kubernetes-native pod scheduling, which narrows the blast radius if a build job is compromised.
That distinction matters when teams compare convenience against isolation. If a pipeline expects nested container builds, Docker in Docker can be easier to wire up. If the priority is reducing privileged access, ARC Kubernetes mode is the safer default because it avoids depending on a privileged daemon socket inside the runner pod.
What Security Trade-Off Changes Between the Two Modes?
The main security trade-off is between flexibility and exposure. Docker in Docker can be efficient for image builds and container-in-container workflows, but the privileged pod model increases the consequences of runner compromise. ARC Kubernetes mode reduces direct host access risk, which makes it easier to enforce tighter isolation between jobs, pods and the cluster node.
For practitioners, the meaningful question is whether the build system genuinely needs daemon-level capabilities. If it does, you should treat the runner as a higher-trust component and harden it accordingly. If it does not, the Kubernetes mode design usually gives a better security posture because the runner does less on the host and relies less on privileged container execution.
That also changes how you think about image provenance and secret handling. A build environment that can talk to a Docker daemon, mount sensitive sockets or run privileged containers creates a larger attack surface than a model that isolates workload pods more cleanly. The same is true for credentials used by the runner, because a compromised privileged runner often has a broader path to registry tokens, cluster permissions or other secrets than an unprivileged pod-based model.
When Should Teams Prefer One Mode Over the Other?
Choose Docker in Docker only when the workflow truly needs daemon semantics, nested container builds or compatibility with tooling that assumes direct Docker access. Choose ARC Kubernetes mode when you want the runner to behave more like an orchestration layer than a host-adjacent build appliance. That makes it a better fit for teams optimizing for least privilege, cluster isolation and simpler containment of a bad job.
Docker Security Checklist is the right companion when you are deciding whether privileged runner settings, daemon access or container runtime flags are acceptable. It helps translate the abstract trade-off into concrete checks on host access, socket exposure, registry credentials and runtime hardening.
Self-hosted CI/CD runners and build agents is useful when the real question is runner isolation, single-use execution and registration credential handling. The underlying control decision is the same: keep the build surface as ephemeral and bounded as possible when jobs come from less trusted code or mixed projects.
Azure Arc Security Guide is relevant where ARC-specific onboarding, agent identity and workload controls determine how much trust the runner should receive. That matters most when the runner is part of a broader hybrid management plane rather than a simple ephemeral build node.
Risk and Threat Considerations
Docker in Docker increases the impact of runner compromise because a privileged build environment can cross from job execution into host-adjacent control. In practice, that means a malicious or broken pipeline step may reach farther than intended, especially if daemon access, mounted sockets or broad credentials are present. ARC Kubernetes mode lowers that exposure by keeping each workload in a separate pod with less direct host power.
Failure mechanism: A privileged runner or exposed Docker daemon lets an attacker turn build-time execution into broader node, registry or cluster access, while an unprivileged pod model limits the same compromise to a narrower execution boundary.
Impact: The likely result is wider secret exposure, easier lateral movement within the build environment and a larger blast radius if a pipeline job is malicious, misconfigured or otherwise compromised.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST SP 800-53 Rev 5 and NIST SP 800-190 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-5 — Account Management | Runner access and privileged execution hinge on tight account control. |
| Recommendation — Restrict runner accounts, remove unused access, and review privileged build identities regularly. | ||
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Privileged Docker execution versus pod isolation is a least-privilege decision. |
| IA-5 — Authenticator Management | Build runners often depend on tokens, keys and registry credentials that must be protected. | |
| CM-7 — Least Functionality | Kubernetes mode reduces unnecessary host functionality compared with privileged Docker execution. | |
| Recommendation — Limit runner permissions to the minimum needed for the build path. Rotate and protect runner credentials, secrets, and registry tokens on a defined lifecycle. Disable unnecessary host features and privileged container capabilities in runner design. | ||
| NIST SP 800-190 | 1.1 — Container image security | The question compares container build/runtime models and their exposure paths. |
| Recommendation — Apply container security guidance to image, runtime, and orchestration choices. | ||
Practitioner Guidance
What to verify: Confirm whether your pipeline actually needs Docker daemon access, privileged mode or nested container execution. If it does not, treat that requirement as an exception that needs justification rather than a default runner setting.
Decision rule: If the runner can build without host-level Docker privileges, prefer ARC Kubernetes mode and keep the build pod as disposable as possible. If privileged Docker is unavoidable, isolate it tightly, restrict who can target it and assume any compromise has higher blast-radius potential.
Practitioner takeaway: The core decision is not Docker versus Kubernetes as abstractions, but whether you are willing to trade runner simplicity for a much larger trust boundary.
Related resources from NHI Mgmt Group
- Guide: ARC Guide
- When should security teams prioritise Kubernetes mode over Docker in Docker for ARC runners?
- How should security teams implement stateful mock services for third-party dependencies in Docker and Kubernetes environments?
- Why do vulnerable container images increase operational risk in Kubernetes and Docker environments?
- How should security teams handle secrets across Jenkins, Docker, Kubernetes, Terraform, and cloud services without losing control?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org