Repository navigation
[workshop] Add node: Running on Actions Runner Controller (ARC) with Docker-in-Docker - #3657
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…ocker Adds a new side quest branching from Step 24 (Self-Hosted Runners) that covers Kubernetes-hosted runner fleets managed by Actions Runner Controller (ARC) and the runner.topology: arc-dind frontmatter field required for agentic workflows to run correctly on ARC's Docker-in-Docker mode. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
This pull request was automatically closed because it expired on 2026-09-22T19:19:30.419Z.
|
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
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.
Adds a new optional side quest, Running on Actions Runner Controller (ARC) with Docker-in-Docker, branching from Step 24: Run Your Agentic Workflow on a Self-Hosted Runner.
This node closes a gap for enterprise learners running Kubernetes-hosted runner fleets: it explains why agentic workflows require ARC's Docker-in-Docker (DinD) mode rather than Kubernetes mode, and walks through setting the
runner.topology: arc-dindfrontmatter field. The existing self-hosted runner content (Step 24 and its infrastructure deep-dive side quest) covers VM-based ephemeral/JIT runners and proxy configuration, but never addresses ARC/Kubernetes topology.Serves enterprise learners on Kubernetes infrastructure, chosen per the enterprise tie-break rule in the workshop guidelines.
workshop/README.mdandworkshop/24-self-hosted-runners.mdare updated with links to the new node.Warning
Firewall blocked 4 domains
The following domains were blocked by the firewall during workflow execution:
github.comgithub.github.comraw.githubusercontent.comregistry.npmjs.orgTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.