Skip to content

Fail closed when GitHub DinD runners lack Docker #13

Description

@linear-code

CD run 30912244798 assigned Build API job 92004418975 to runner creativetoolkits-dind-runners-m2rbw-runner-vnn8t even though its Docker daemon never became available. docker/setup-buildx then failed on /var/run/docker.sock. The shared DinD template sets RUNNER_WAIT_FOR_DOCKER_IN_SECONDS, but the upstream runner helper proceeds after that wait expires.

Scope: make the shared DinD runner bootstrap fail closed before registration when docker info cannot succeed. Do not change or work around the separate production Prisma migration failure.

Acceptance:

  • A DinD runner cannot accept a GitHub job until docker info succeeds.
  • A permanently unavailable daemon causes the runner container to fail rather than register.
  • The GitHub Actions Helm chart renders and validates.
  • A fresh Docker-enabled Actions job succeeds on the deployed runner scale set.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions