fix(docker): correct stale --db-path comments in fetch/git Dockerfiles and clarify git README
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- docker, typescript
- Domain
- devops, documentation
Research direction
Read src/fetch/Dockerfile, src/git/Dockerfile, and src/git/README.md at the cited locations. Remove the fetch database-path comment, update the git Dockerfile comment to describe mounting the host repository directory, and correct the README’s description of the container user. Done when all three descriptions match the setup described in the issue.
Written by the indexing model from the issue text.
Description
Which server?
More than one server
Server version
n/a
How did you run the server?
Docker image
Transport
Not applicable (a repository-level report)
Protocol era
Not applicable (a repository-level report)
MCP client and version
n/a
Operating system and runtime
Docker / Linux
Server configuration
No response
Steps to reproduce
- Inspect
src/fetch/Dockerfileat line 38:
# when running the container, add --db-path and a bind mount to the host's db file - Inspect
src/git/Dockerfileat line 41:
# when running the container, add --db-path and a bind mount to the host's db file - Inspect
src/git/README.mdat line 204:
Mentions that "The image runs as root, so it goes at /root/.gitconfig:", whereas the Dockerfile sets up the non-rootappuser (useradd -rUM -s /usr/sbin/nologin app).
Expected behavior
src/fetch/Dockerfile: The--db-pathcomment should be removed as thefetchserver is an HTTP client without database arguments or host DB mounts.src/git/Dockerfile: The comment should refer to bind-mounting the host repository directory, not a database path.src/git/README.md: Documentation should accurately reflect the container's user execution model.
Actual behavior
Both Dockerfiles retain a copy-pasted comment from database servers referencing --db-path and database mounting.
Logs or error output
Already prototyped a fix?
In src/fetch/Dockerfile:
Remove the outdated comment on line 38 (# when running the container, add --db-path and a bind mount to the host's db file).
In src/git/Dockerfile:
Update line 41 to reference mounting the host's git repository directory.
Before you submit
- I searched existing issues and this is not a duplicate.
- This is not a security vulnerability report (those go through the private advisory form).
- Dominant language
- TypeScript
- Stars
- 91.7k
- Forks
- 11.9k
- Avg merge
- 3h 30m
- Merged PRs (30d)
- 204
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/servers
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
modelcontextprotocol/servers#5482 ·
Maintainers usually reply within 1 day
-
chore dependencies server-filesystem v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5481 · 1 comment ·
Maintainers usually reply within 1 day
-
chore v2
Difficulty 4/5 3-5 days Newbie friendliness 45/100
modelcontextprotocol/servers#5463 ·
Maintainers usually reply within 1 day
-
bug server-filesystem v2
Difficulty 5/5 Over a week Newbie friendliness 25/100
modelcontextprotocol/servers#5260 · 3 comments ·
Maintainers usually reply within 1 day
-
git: the string "null" for base_branch, contains or not_contains arrives as None (python-sdk#3055)Openbug server-git v2 waiting-on-sdk
Difficulty 3/5 1-2 days Newbie friendliness 68/100
modelcontextprotocol/servers#5176 · 1 comment ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/servers
Similar issues
-
Navbar avatar and name stay stale after saving profile changesPossibly taken @alexechoi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
marmelab/atomic-crm#416 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epam/ai-dial-react-file-manager#99 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
canonical/craft-actions#146 ·
Maintainers usually reply within 2 days
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
bluesky-social/social-app#12343 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lucide-icons/lucide#5165 ·
Maintainers usually reply within 1 day