You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BuildKit honors .dockerignore for --mount=type=bind sources, so the bind mount cannot find .git in the context and the build fails.
This was likely not caught pre-merge because cached image layers from before .dockerignore was added masked the failure on maintainer machines. A fresh clone + first build hits it immediately.
Reproduction
git clone https://github.com/eigent-ai/eigent.git
cd eigent/server
cp .env.example .env
docker compose build --no-cache api # or `docker compose up --build -d`
Environment
macOS (Darwin 25.5.0), Docker Desktop with BuildKit enabled (default)
Summary
Following
server/README_EN.mdstepdocker-compose up --build -d(from a clean state, no cached layers) fails on the API image build:Root cause
A regression introduced in the 1.0.0 release.
server/Dockerfile:66(added in PR feat: detect stale local server and notify developer to restart #1517, March 2026) bind-mounts.gitfrom the build context to stamp the server commit into the image:.dockerignorewas added new in commit 97d7554 (release: Eigent 1.0.0, PR release: Eigent 1.0.0 #1695) and excludes.git:.dockerignorefor--mount=type=bindsources, so the bind mount cannot find.gitin the context and the build fails.This was likely not caught pre-merge because cached image layers from before
.dockerignorewas added masked the failure on maintainer machines. A fresh clone + first build hits it immediately.Reproduction
Environment
Fix
Stop ignoring
.gitin.dockerignore. The bind mount means.gitis never baked into a layer, only made available during the build step. PR to follow.