Docker builds are broken due to missing files or invalid flags
11 posts in the last 30 days, all from GitHub.
“What Dockerfile L2 7 and L22 29 copy package .json and run npm ci ignore scripts , but the repository's only lockfile is bun.lock . .dockerignore L21 excludes bun.lock from the build context, and package lock.json does not exist anywhere in the tree (it was removed in the bun…”
“🔴 Docker Build is failing on main . Broken since 6955d7b — 5 consecutive failures. | run | commit | author | PR | | | | | | | 10480 | 6955d7b | Brad Hoekstra | 2724 | | 10488 | 031a613 | Ginny | 2357 | | 10489 | 72def2d | bnaylor | 2734 | | 10495 | c111d2a | Brad Hoekstra |…”
“🔴 Docker Build is failing on main . | run | commit | author | PR | | | | | | | 9528 | f140d79 | Talha | 2425 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
Several users report Docker build failures stemming from issues like nonexistent files (Dockerfile, migrations), incorrect CLI flags, and references to non-existent files within the compose setup. These problems prevent successful image creation and require manual intervention.
SOURCES (21)
“What Dockerfile L2 7 and L22 29 copy package .json and run npm ci ignore scripts , but the repository's only lockfile is bun.lock . .dockerignore L21 excludes bun.lock from the build context, and package lock.json does not exist anywhere in the tree (it was…”
“Dockerfile copies requirements.txt (removed in 9a9262f) and uses python:3.9 while requires python =3.10 . Rebuild it on a 3.10+ image using uv/pyproject.”
“🔴 Docker Build is failing on main . Broken since 6955d7b — 5 consecutive failures. | run | commit | author | PR | | | | | | | 10480 | 6955d7b | Brad Hoekstra | 2724 | | 10488 | 031a613 | Ginny | 2357 | | 10489 | 72def2d | bnaylor | 2734 | | 10495 | c111d2a | Brad Hoekstra | 2788 | | 10507 | 8b4c934 | toshiowang | 2822 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
“🔴 Docker Build is failing on main . | run | commit | author | PR | | | | | | | 9528 | f140d79 | Talha | 2425 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
“🔴 Docker Build is failing on main . | run | commit | author | PR | | | | | | | 8946 | c2ad636 | Fuxiao G | 2291 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
“Problem Both Dockerfiles reference packages that don't exist post rebrand: turbo filters @activepieces/engine and web (real names: @inboxfm connect/engine , @inboxfm connect/web ), a worker package that isn't in the repo at all, and a find over the deleted packages/pieces tree. The fork cannot build its own container image; it currently works only by pulling upstream's image. Evidence Dockerfile:75 — RUN npx turbo run build filter=web filter=@activepieces/engine filter=api filter=worker packages”
“The Dockerfile has drifted from the crate: FROM rust:1.79 , but Cargo.toml has rust version = "1.85" . It copies /app/target/release/orchestrator demo , which no longer exists. The binary is orchestrator . It only copies src and examples , but Cargo.toml declares [[bench]] targets under benches/ , so the manifest will not load. It builds with features metrics server only, so the REST API on 8080 is missing, and only 9090 is exposed. Done when docker build . succeeds and docker run p 8080:8080 e”
“🔴 Docker Build is failing on main . | run | commit | author | PR | | | | | | | 6933 | a5b42b3 | Dmitry Shnayder | 1917 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
“Evidence (Docker up, clean checkout of c2cb795 ): Cause: compose resolves its project directory to the directory of the compose file it is given ( deploy/compose/ ), so the repo root .env is not read. Every documented path ( README.md , docs/deploy/quickstart.md , docs/deploy/configuration.md , deploy/vm/quickstart.md ) and scripts/bootstrap vm.sh hit this. Fix in progress: pass env file .env explicitly everywhere + one command scripts/selfhost.sh ( make selfhost ). Regression test: assert the d”
“🔴 Docker Build is failing on main . Broken since 4231682 — 9 consecutive failures. | run | commit | author | PR | | | | | | | 6196 | 4231682 | bnaylor | 1775 | | 6197 | b0efba8 | Hang Duong | 1780 | | 6198 | 0e6e752 | Haoxu Wang | 1360 | | 6199 | 7059a3c | Hang Duong | 1744 | | 6200 | 817e8a3 | Kube Agents Robot | 1792 | | 6202 | 33abd91 | Kube Agents Robot | 1787 | | 6203 | 4afb8ca | kirill kosov | 1796 | | 6242 | 02d5143 | Kube Agents Robot | 1786 | | 6245 | e1bda9f | kirill kosov | 1806 | Op”
“🔴 Docker Build is failing on main . | run | commit | author | PR | | | | | | | 6199 | 7059a3c | Hang Duong | 1744 | Opened and closed automatically by main broken notify.yml . It closes when Docker Build next passes on main ; a failure after that opens a new issue.”
“Problem The container deliverable — a documented delivery mode — cannot run either entrypoint. 1. [CRITICAL] CLI symlink dead (Dockerfile:54): targets /app/packages/bridge cli/dist/src/bin/bridge.js but tsconfig rootDir:'src' emits dist/bin/bridge.js (verified on disk) → docker run … bridge <cmd fails, guaranteed. The governance example workflow gets the right path — align. 2. [CRITICAL] registry service symlink dangling (Dockerfile:55 + package.json:22): root build never builds @bridge/registry”
“What's broken pnpm build (and therefore docker compose up build , which runs it in app/Dockerfile ) currently fails with 198 TypeScript errors, entirely pre existing and unrelated to 96 (verified by stashing that branch's changes and re running against the unmodified tree the error count and file list are effectively unchanged). pnpm lint 's own tsc noEmit step doesn't catch this: the root tsconfig.json has files: [] and isn't invoked in b (project reference/build) mode the way pnpm build 's tsc”
“Build root Dockerfile fails on every open PR against dev , including PRs that touch only Python. It is not caused by any of them. Dockerfile:206. Evidence that it is dev , not the PRs | PR | touches | Build root Dockerfile | | | | | | 1274 | evaluator.py + a test | FAIL | | 1272 | browserslist bump | FAIL | | 1270 | github actions bump | FAIL | | 1268 | node digest bump | passed while stale, FAILS once rebased on current dev | | 1269 | chainguard/python digest bump | SUCCESS | 1268 is the tell:”
“Bug Report: docker compose references a YAML file not present in the current working directory”
“Bug Description docker compose build fails building the localai n8n runner 1 image with: exit code: 126 Root cause Upstream image n8nio/runners:stable (digest sha256:9ddeb7c4797f5bda2aa746364848e9e8c5f8f50b8355e05e6ac5e5ee9183eaf9 , rebuilt 2026 09 02 07:31 UTC) ships pnpm without the execute bit: /usr/local/bin/pnpm is a symlink to that file (mode 0644). Even as root: while node /usr/local/lib/node modules/pnpm/bin/pnpm.cjs version works fine (pnpm 11.22.0). The RUN in Dockerfile.runner execute”
“Problem Building images from a clean checkout does not work: console fails outright. worker builds but the container exits immediately. scripts/release images.sh does not point at the paths correctly. .dockerignore files are never read. The images published on Docker Hub are unaffected, so this only hits contributors and anyone building from source. Proposed solution In console/Dockerfile , delete the two COPY lines for paths that are not in the repo. In worker/Dockerfile , install the binary un”
“docs/operations/DEPLOY PRODUCTION.md:113 sends operators to a command that cannot run: scripts/ops/verify monitoring.sh:7 sets but that file does not exist on origin/main . The production compose file is deploy/docker compose.prod.yml . With set euo pipefail at the top, the script fails as soon as it uses $COMPOSE FILE . Impact: the monitoring verification step of the production deploy runbook has been broken since 3b723dc87 . docs/notes/SOC A1.1 CAPACITY NOTES.md:146 additionally cites this scr”
“docker compose up fails at the pnpm install frozen lockfile step, so the Docker dev workflow documented in CLAUDE.md ("Always run all local tests using Docker") does not currently work. Error Cause Dockerfile.dev uses a Node 20 base image. package.json has a packageManager /corepack path that resolves to pnpm 11.13.0, which requires Node = 22.13 and imports node:sqlite — a module that does not exist in Node 20. Notes CI is unaffected: .github/workflows/ci.yml uses Node 20 with pnpm/action setup@”
“Severity: Critical (file is unusable) compose/docker compose.yml: :94 dockerfile: docker/Dockerfile — no such file (only ./Dockerfile) → build fails :126 command uses mode paper — flag doesn't exist in the CLI; combined with the image ENTRYPOINT it also yields python m python m ... :17 bind mount ./migrations resolves relative to compose/ → compose/migrations (nonexistent) → DB init SQL silently never applied docs/RUNBOOK.md §3 still references this file ("tracing" profile lives here). Fix Delet”
“Severity: MEDIUM (correctness) Area: Dockerfile Location: Dockerfile:53 and Dockerfile:9,71 Summary Two independent problems break docker build : 1. Line 53: COPY ./package.json ./package lock.json ./ — the repo has no package lock.json ; it uses pnpm ( pnpm lock.yaml ). The COPY step fails immediately, so the image cannot be built from this repository as is. 2. Lines 9/71: ARG DATABASE CLIENT=podcastmanager — not a valid client. config/database.ts only defines a postgres connection and looks it”
