g1t/services/runner/Dockerfile
Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 1 | # syntax=docker/dockerfile:1.7 |
| 2 | # | |
| 3 | # The sandbox a g1t agent works in, and where workflow jobs and g1t.page | |
| 4 | # builds run: the base image (services/runner/base/Dockerfile, everything | |
| 5 | # but the runner) and the g1t runner, a static Linux binary built outside | |
| 6 | # Docker by scripts/build-runner.mjs. | |
| 7 | # | |
| 8 | # Built by scripts/deploy.mjs, which passes BASE (the image recorded in | |
| 9 | # services/runner/base.json) and uses a build context holding only the | |
| 10 | # binary, so this takes seconds. docs/DEPLOYING.md explains the two images. | |
| Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed) | 11 | |
| Fast pages, required checks on the branch, self-hosted runners, honest incidents | 12 | ARG BASE |
| 13 | FROM ${BASE} | |
| 14 | COPY --chmod=0755 g1t-runner /usr/local/bin/g1t-runner | |
| Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed) | 15 | ENTRYPOINT ["g1t-runner"] |