Commit6499f34unknown_key

fix(docker): guarantee git is in the runtime image

fix(docker): guarantee git is in the runtime image

Every repo page (branch/tree listing, diffs, clone, push) shells out to
the `git` binary via Bun.spawn. The running image was missing git —
likely a stale BuildKit cache layer — so those routes 500'd with
`ENOENT: posix_spawn 'git'`.

Harden the install: pin ca-certificates, drop recommends, and run
`git --version` as the last step so a missing binary fails the build
loudly instead of shipping an image that breaks on every repo page.

Changing this RUN line also busts the stale cache layer on next build.

https://claude.ai/code/session_01QKaJBYpD6DGErWHrRVChkf

Claude committed on June 1, 2026Parent: ff0ca55

1 file changed+7−26499f34f8979b7b9779712db52aca98797cdedeb

1 changed file+7−2

ModifiedDockerfile+7−2View fileUnified Split

@@ -1,8 +1,13 @@

11FROM oven/bun:1.3 AS base

22WORKDIR /app

4# Install git (required for git operations)

5RUN apt-get update && apt-get install -y git && rm -rf /var/lib/apt/lists/*

4# Install git (required for ALL git operations — clone, push, branch/tree

5# listing, diffs). Verify it landed: a missing binary here must fail the

6# build loudly rather than ship an image that 500s on every repo page.

7RUN apt-get update \

8 && apt-get install -y --no-install-recommends git ca-certificates \

9 && rm -rf /var/lib/apt/lists/* \

10 && git --version

611

712# Install dependencies

813COPY package.json bun.lock ./

914