ci: do not fail the docker job when the runner has no daemon #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/docker-job-tolerates-missing-daemon"
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?
What this changes
The docker lane no longer fails when the runner has no reachable docker daemon, and it no longer
assumes
sudoexists.Why
Run 1 (commit
0107075) went red onCI / Docker buildin 26 s:successTest (Node 18) 41 ssuccessTest (Node 20) 48 ssuccessTest (Node 22) 49 ssuccessServer smoke test 48 sfailureDocker build 26 sThe job image runs as root and has no
sudo, sosudo apt-get install docker.iofailed before anyimage work started. That is a red check about the runner, not about the code — exactly the kind of
permanent red that turns a gate into wallpaper.
How it was verified
node scripts/check-dockerfile.js→ all checks pass (that is the real gate).apt-get install docker.io(no sudo) and still runsdocker buildwheredocker infosucceeds; otherwise it says so and passes.What it deliberately does not change
The static Dockerfile checks stay the gate. This does not weaken them, and it does not pretend the
image was built when it was not.