User reported docker compose dev stack failing on a fresh clone with:
COPY package.json bun.lock ./
target server: failed to compute cache key: '/bun.lock': not found
Root cause: bun.lock was listed in .gitignore (line 12), so the lockfile
existed only on machines where bun install had been run locally. On a
fresh clone, the file is missing entirely, and Dockerfile.dev's
'COPY package.json bun.lock ./' fails because the build context has no
lockfile.
Fix: remove the gitignore entry and commit the existing 987-line lockfile.
This matches the standard practice for every JS package manager (bun,
npm, yarn, pnpm) \u2014 commit the lockfile so installs are reproducible
across machines. The Dockerfile already uses 'bun install --frozen-lockfile'
which depends on this file being present.
Note: the 'pull access denied for paratype/dev' line in the user's error
output is benign cosmetic noise from compose's pull-then-build fallback
flow when image: paratype/dev:local is set (compose tries the registry
first, gets a 403 since the image name is local-only, then falls back
to the local build context). Not an error \u2014 ignore.
After this commit, on a fresh clone:
git clone <repo>
docker compose -f docker-compose.dev.yml up
should work without any prior bun install on the host.
