fix(images): name the measured runner blocker; the job container gets no Docker daemon
PR #81's first images run failed in 6s: act_runner 0.2.11 forces docker_host '-' for a tcp:// DOCKER_HOST, and gitea/act drops every bind when valid_volumes is empty. Giving jobs the privileged DinD daemon is node-root for any workflow author, so it is left to the operator; options are in the handoff entry. The driver's failure now names the cause. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
e539109830
commit
8f35234fcc
3 files changed
+80
-5
No files matched your search
@@ -41,6 +41,15 @@
|
||||
# not checked by Gitea (basic.go resolves the owner from the token), so `vars.REGISTRY_PUSH_USER`
|
||||
# is optional and only labels the login.
|
||||
#
|
||||
# ┌─ BLOCKER, MEASURED ON PR #81 (run 325): THIS RUNNER CANNOT BUILD IMAGES YET ───────────────┐
|
||||
# │ The job container gets no Docker daemon. act_runner 0.2.11 forces container.docker_host to │
|
||||
# │ "-" whenever DOCKER_HOST is tcp:// (internal/app/cmd/daemon.go), and with valid_volumes: [] │
|
||||
# │ gitea/act strips every bind including the socket (pkg/container/docker_run.go │
|
||||
# │ sanitizeConfig). So this job fails at its first check, loudly, until the operator chooses │
|
||||
# │ how workflow code may reach a daemon — see decisions/2026-10-29-image-pipeline.md. It is │
|
||||
# │ not a required check, so it does not block merges; it is red, which is the honest state. │
|
||||
# └──────────────────────────────────────────────────────────────────────────────────────────────┘
|
||||
#
|
||||
# THE RUNNER (apps/wave-1/gitea-actions.yaml): act_runner 0.2.11, one job at a time, Docker
|
||||
# executor on a privileged `docker:27-dind` sidecar whose image store is an emptyDir on the node
|
||||
# (no sizeLimit) and whose memory limit is 2Gi — shared by the job container AND every build
|
||||
|
||||
Reference in new issue
Block a user