Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[workshop-sync] side-quest-24-01-runner-infrastructure.md: ephemeral/JIT runner and proxy-env-var guidance unsupported by self-hosted-runners re

Aperta Adatta ai principianti
  • Qualcosa non va?
#4,449 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
78/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
documentation

Direzione di ricerca

Inizia da workshop/side-quest-24-01-runner-infrastructure.md e confronta le indicazioni su runner e rete con il riferimento collegato sui self-hosted-runners. Aggiorna le sezioni su ephemeral/JIT e proxy in modo che corrispondano alla configurazione documentata dei runner e all’isolamento di rete, e allinea la spiegazione del server MCP a network.allowed. Il lavoro è completato quando le affermazioni inesatte sono corrette e gli esempi corretti elencati nell’issue restano intatti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation

Workshop file reviewed

workshop/side-quest-24-01-runner-infrastructure.md

Problem

  1. The "Ephemeral and JIT runners" section states:

Ephemeral runners are destroyed after a single job ... Register one using the ephemeral flag ... Just-in-time (JIT) runners are provisioned on demand and deregistered immediately after use. They require a registration token scoped to your organisation or repository and are typically managed by a runner controller such as actions-runner-controller.

This section links to https://github.github.com/gh-aw/reference/self-hosted-runners/, but that page contains no mention of ephemeral runners, JIT runners, registration tokens, or actions-runner-controller registration flags.

  1. The "Proxy and network requirements" section instructs learners to set host-level proxy environment variables:
HTTPS_PROXY=(proxy.example.com/redacted)
HTTP_PROXY=(proxy.example.com/redacted)
NO_PROXY=localhost,127.0.0.1,github.example.com

This is not documented anywhere in the gh-aw reference docs as the mechanism for self-hosted runner network configuration.

  1. The "Network isolation" section frames "MCP tool servers" as independently-reachable endpoints, separate from network.allowed.

Current correct behaviour

The actual reference/self-hosted-runners/ page documents:

  • The runs-on frontmatter field (string/array/object forms) to target self-hosted runners.
  • require_self_hosted_runners in .github/workflows/aw.json (or --require-self-hosted-runners CLI flag) to enforce self-hosted runners on all generated jobs.
  • ARC Docker-in-Docker topology via runner.topology: arc-dind, including GH_AW_DOCKER_SOCK_PATH/GH_AW_DOCKER_SOCK_GID env var overrides for split-daemon setups.
  • Network isolation is enforced via AWF's own internal Docker network topology (an internal awf-net bridge with no internet route) and a dual-homed Squid proxy inside the Docker daemon's domain — not via host-level HTTPS_PROXY/HTTP_PROXY/NO_PROXY env vars on the runner machine.
  • Documented outbound network requirements: api.githubcopilot.com (or enterprise Copilot endpoint), github.com (or GHES instance), ghcr.io (to pull the MCP gateway image), and any domains in network.allowed.

Suggested fix

  • Remove or rewrite the "Ephemeral and JIT runners" section to cover gh-aw-documented self-hosted runner configuration instead: runs-on, require_self_hosted_runners, and runner.topology: arc-dind for ARC DinD setups.
  • Replace the HTTPS_PROXY/HTTP_PROXY/NO_PROXY guidance with an explanation of AWF's internal Squid-proxy network isolation and the documented outbound endpoint list (Copilot/model endpoint, GitHub/GHES, ghcr.io, plus network.allowed domains).
  • Reframe "MCP tool servers" access as governed by the network.allowed frontmatter field rather than a separately reachable endpoint category.
  • The network.allowed example and firewall.md artifact mention in this file are accurate and do not need changes.

Reference: https://github.github.com/gh-aw/reference/self-hosted-runners/ (confirmed reachable, HTTP 200; verified no "ephemeral"/"JIT"/proxy-env-var content present)

Generated by 🔍 Workshop Sync Check · copilot · auto · 239.5 AIC · ⌖ 8.28 AIC · ⊞ 9.2K · ◷

  • expires on Oct 12, 2026, 5:49 AM UTC
Lingua principale
JavaScript
Stelle
52
Fork
26
Merge medio
12h 58m
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.