Docker Image 1.0.2 Breaks Linux Users with Letter at Start of Path #3628

Activity

1. jvanvolken

   added

   bugSomething isn't workingSomething isn't working

   on Mar 18, 2026
2. owendevereaux commented on Mar 19, 2026

   

   owendevereaux

   on Mar 19, 2026

   More actions

   I investigated this issue and found something interesting:

   Looking at the current path-utils.ts on main, the code appears to handle Linux paths correctly:

   const isUnixPath = p.startsWith('/') && (
     p.match(/^\/mnt\/[a-z]\//i) ||
     (process.platform !== 'win32') ||  // Should be TRUE in Linux Docker
     ...
   );

   On a Linux Docker container, process.platform === 'linux', so the condition (process.platform !== 'win32') should be true, which should preserve Unix paths like /h/username/... without converting them to Windows format.

   Question: Is there a chance the mcp/filesystem:1.0.2 Docker image was built from an older version of the code that didn't have this platform detection logic? The fix may already exist on main but not be in the released Docker image.

   If so, rebuilding the Docker image from the current main branch might resolve this issue.

   (I noticed the package tags are typescript-servers-0.6.x while the Docker image uses 1.0.2 versioning, so there may be a versioning/release pipeline difference.)
3. jvanvolken commented on Mar 26, 2026

   

   jvanvolken

   on Mar 26, 2026

   Author

   More actions

   Sorry for the delayed response to your question(s).

   I'm not sure what was included in the 1.0.2 image, we just know it doesn't work for our use-case. The image versioning is not automatically tied to the main branch versioning, wish it was!

   I would normally love to rebuild the image myself, however in our particular air-gapped environment its easier to get images from Docker hub approved versus the alternative you're suggesting.
4. majiayu000 commented on Apr 3, 2026

   

   majiayu000

   on Apr 3, 2026

   More actions

   Hi, I've been looking into this and traced the root cause.

   Proposed approach: 1. Verify whether path-utils.ts on main already has the correct platform detection logic. 2. If the fix exists on main, this may be a Docker image build/release issue rather than a code fix — check if the Docker image build process pulls from the correct branch/tag. 3. If code changes are needed, fix path normalization in path-utils.ts to properly detect Linux platform in Docker containers and preserve Unix-style paths (especially paths starting with /h/, /u/, etc. that could be misinterpreted as Windows drive letters). 4. Add tests for Linux path handling in Docker context.

   I'll open a draft PR shortly. Happy to adjust based on your preference.
5. majiayu000

   added a commit that references this issue on Apr 3, 2026

   test(filesystem): add regression tests for Docker Linux path handling

   ...

   90a0c8f