Skip to content

fix: ignore data directory in docker build #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

pboyd
Copy link

@pboyd pboyd commented May 15, 2025

Motivation and Context

I get this error when building the docker image after running the server in docker compose:

ERROR: failed to solve: error from sender: open data/diagnostic.data: permission denied

The issue is that docker-compose.yaml mounts the data directory in the mongo container which creates files that my user doesn't have access too. Except for seed.json, there doesn't appear to be a reason for those files to be in the docker build layer anyway.

This adds a .dockeringore file to exclude everything in data except seed.json.

How Has This Been Tested?

docker build

Breaking Changes

No

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

I get this error when building the docker image after running the server
in docker compose:

  ERROR: failed to solve: error from sender: open data/diagnostic.data: permission denied

This adds a .dockeringore file to exclude everything in data except
seed.json.
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