TOP PRIORITY: docker build . fails on next
#261
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sneak/upaas#261
Reference in New Issue
Block a user
Owner (chat, 2026-10-01 ~23:03 UTC):
Standing rule from the same hour (sneak/project-management#20):
mainandnextare green on every managed repo at all times, and any divergence is top priority. This comes before all other upaas work.Definition of done:
nexthead (docker build .in the repo root, plusscript/cibuildormake check), and post the failing step and its cause here in a few lines.nextwith an independent review, rebased ontonextright before the review, then squashed. Never weaken a test.docker build .and the check pass on a fresh clone of the newnexthead. One line here says so, with the SHA.model: opus-5-5
Not reproduced yet. On a fresh clone of
nextat5ca1bce,docker build .succeeds here (Docker Engine 29.8, linux/amd64), andmake checkpasses on the same tree. The merge commit5ca1bcechanges no files compared with9488e2f, so it is not the cause.So the failure depends on the machine or the working copy it runs in. The leading suspect: since #236 (
a48d90f),.dockerignoresends the working copy's whole.gitdirectory and every git-ignored file except.env,bin/,.vscode/,.idea/and*.testinto the build. A fresh clone has none of those local files, and the review of 236 gated only fresh clones, which is why it passed.@sneak: which step fails, and with what error? The last 20 or so lines of
docker build --progress=plain ., plus the machine (OS, CPU) anddocker version, are enough. Until then a worker is checking the build against a working copy with typical local files.Model: opus-5-5
Still not reproduced, on
nextat7685812. Tried here:docker build .andmake dockerfrom a working copy set up like a developer's:make bootstraprun (sonode_modules/exists), git-ignored local files (.env.local, a*.key, a*.out,.DS_Store), thedata/directory upaasd creates when run from the checkout, and an uncommitted change. The build does not fail.make test, run as the build runs it, on one CPU and on two: every package stays far inside the 30-second limit, so a slower machine is not the cause..gitthat is a file pointing outside the checkout, andcore.fsmonitorset in.git/configas on macOS: neither breaks the build.Not tested: an arm64 machine such as an Apple Silicon Mac (no emulation on this host).
None of the 2026-10-01 merges, #256 included, changes the
Dockerfile,.dockerignore, theMakefile,script/or the dependencies. The only change onnextthat makes the build depend on the working copy is #236 (a48d90f, 2026-09-29).Found on the way, not this failure: since #236 the build stages receive the working copy's git-ignored secrets (
.env.local,*.key,data/session.key); the final image holds only the binary.data/, the default data directory, is not git-ignored.No fix opened: there is no known cause to fix. @sneak: still needed are the last 20 or so lines of
docker build --progress=plain .from the copy where it fails, and the machine (OS, CPU).Model: opus-5-5
nextatd3b9c6fpassesdocker build .andmake checkon a fresh clone here. Since the last report two changes narrowed what the build receives from a working copy: git-ignored files anddata/stay out (#266) and so does.git/config(#269). If the failure came from local files in your copy, it may be gone.@sneak: please run
docker build --progress=plain .again ond3b9c6fwhere it failed; if it still fails, the last 20 or so lines and the machine (OS, CPU) are what is needed.Model: opus-5-5