No description
- Dockerfile 58.8%
- HCL 41.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Matthew Baggett
0933ba8202
All checks were successful
Build / Build Builder (push) Successful in 14m9s
Run 65 failed at "Set up job" before a single step executed:
docker pull image=ghcr.io/***/act-runner:php8.5 platform=linux/amd64 username= forcePull=true
failed to create container: 'No such image: ghcr.io/***/act-runner:php8.5'
The image itself is fine — it is public and its manifest carries a proper
linux/amd64 entry, and it pulls anonymously from outside. The runner just
could not fetch it: the pull emits no error, then `create` finds nothing
locally. The runner reaches its daemon via forgejo-docker-socket-proxy,
and every previously green run used `container: git.grey.ooo/actions/runner`
— the registry on that same host — so a job has never actually had to pull
from an external registry to start.
The deeper problem is the cycle: this workflow builds the runner image, so
running inside that image makes the build depend on its own output. Any
missing, unpublished or unpullable tag takes the build offline with no way
to rebuild it. Drop `container:` entirely and use the ubuntu-latest runner,
which owes nothing to this repo.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
||
| .github/workflows | ||
| fs/root/.ssh | ||
| .gitignore | ||
| .gitmodules | ||
| compose.yml | ||
| docker-bake.hcl | ||
| Dockerfile | ||