fix: exclude .workspace from Docker build context (#304)#305
Merged
bussyjd merged 1 commit intoMar 30, 2026
Conversation
When OBOL_DEVELOPMENT=true, Docker builds from the project root pick up .workspace/data/ directories that contain root-owned PVC mounts from previous clusters, causing "permission denied" errors during context scanning. Exclude .workspace/ and .worktrees/ from the Docker build context via .dockerignore. Fixes #304
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.dockerignoreat the repo root to exclude.workspace/and.worktrees/from Docker build contextpermission deniederrors whendocker buildscans root-owned PVC directories under.workspace/data/Fixes #304
Test plan
OBOL_DEVELOPMENT=true obol stack upon a machine with leftover.workspace/data/PVC directories and confirm Docker builds succeed.dockerignoredoes not exclude.git/(some builds may need git metadata)