feat(github-runner): pod-env DOTNET_INSTALL_DIR + initContainer for non-root runner #7
Reference in New Issue
Block a user
Delete Branch "chore/runner-pod-env-dotnet-install-dir"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Sprint 30 Cl-1 acceptance fix: retires the per-workflow
DOTNET_INSTALL_DIRpatch ~25 flipped Linux repos currently carry by setting it (plus 4 sibling env vars) directly on bothgithub-runnerDeployments.Changes
Both
github-runnerandgithub-runner-sharedposDeployments now have:initContainers.setup-runner-home(busybox:1.36 as UID 0) thatmkdir -p+chown -R 1001:1001/home/runner/.dotnet+/home/runner/.nugetbefore the main container starts.runner-homeemptyDirvolume mounted at/home/runner(the PVC mount at/home/runner/.nuget/packageson the Common runner continues to win at its nested path, so the persistent NuGet cache survives ephemeral restarts).DOTNET_INSTALL_DIR=/home/runner/.dotnet,NUGET_PACKAGES=/home/runner/.nuget/packages,DOTNET_CLI_TELEMETRY_OPTOUT=1,DOTNET_NOLOGO=1,DOTNET_GENERATE_ASPNET_CERTIFICATE=false.Validation
python -c yaml.safe_load_allon the file loads 6 docs cleanly.kubectl apply --dry-run=client -f ...reports all 6 resourcesconfigured (dry run).env vars: 12 | initContainers: 1 | volumes: 3 | volumeMounts: 3and all 5 expected env vars present.Test plan
kubectl -n github-runner get pod -l app.kubernetes.io/name=github-runnerand-l app.kubernetes.io/name=github-runner-sharedposshow pods Running with the new env vars visible in-o jsonpath.dotnet restore-bearing workflow on either runner succeeds without a per-workflowDOTNET_INSTALL_DIRstep.Diff: 92 insertions / 0 deletions (pure additive).
?? Generated with Claude Code