Skip to content

fix(dockerignore): exclude local-only artifacts from build context#10015

Merged
mudler merged 1 commit into
mudler:masterfrom
richiejp:fix/dockerignore
May 26, 2026
Merged

fix(dockerignore): exclude local-only artifacts from build context#10015
mudler merged 1 commit into
mudler:masterfrom
richiejp:fix/dockerignore

Conversation

@richiejp
Copy link
Copy Markdown
Collaborator

Description

Stop docker from transfering GBs of build output into the context

Notes for Reviewers

The build context shipped to the daemon included several large
untracked directories the image never needs: saved image tarballs
(backend-images), locally-installed backends (local-backends), the
host-built binary (local-ai), the rust target/ build output, and
host node_modules/protoc/tests. This bloated the context to ~23GB.

Exclude them so only the sources the Dockerfile actually copies are
transferred. backend/rust sources stay tracked; only target/ is ignored.

Assisted-by: Claude:claude-opus-4-7 [Claude Code]
Signed-off-by: Richard Palethorpe io@richiejp.com

Signed commits

  • Yes, I signed my commits.

The build context shipped to the daemon included several large
untracked directories the image never needs: saved image tarballs
(backend-images), locally-installed backends (local-backends), the
host-built binary (local-ai), the rust target/ build output, and
host node_modules/protoc/tests. This bloated the context to ~23GB.

Exclude them so only the sources the Dockerfile actually copies are
transferred. backend/rust sources stay tracked; only target/ is ignored.

Assisted-by: Claude:claude-opus-4-7 [Claude Code]
Signed-off-by: Richard Palethorpe <io@richiejp.com>
@mudler mudler merged commit 9d90e04 into mudler:master May 26, 2026
54 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants