fix(docker): correct stale --db-path comments in fetch/git Dockerfiles and clarify git README

Open Beginner friendly
#5,483 0 comments 0 reactions 0 assignees View on GitHub

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

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

bug v2
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
  1. Inspect src/fetch/Dockerfile at line 38:
    # when running the container, add --db-path and a bind mount to the host's db file
  2. Inspect src/git/Dockerfile at line 41:
    # when running the container, add --db-path and a bind mount to the host's db file
  3. Inspect src/git/README.md at line 204:
    Mentions that "The image runs as root, so it goes at /root/.gitconfig:", whereas the Dockerfile sets up the non-root app user (useradd -rUM -s /usr/sbin/nologin app).
Expected behavior
  • src/fetch/Dockerfile: The --db-path comment should be removed as the fetch server 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/servers

All issues in modelcontextprotocol/servers

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.