Windows plugin path created as literal directory name in Linux Docker container

Resolved 💬 3 comments Opened Feb 9, 2026 by SendiMyrkr Closed Feb 13, 2026

Description

When running Claude Code inside a Linux Docker container with the .claude config directory mounted from a Windows host, a directory with a mangled Windows path name is created in the workspace (CWD).

Steps to reproduce

  1. Run Claude Code on Windows, allowing it to populate %USERPROFILE%\.claude\ (including plugins/marketplace)
  2. Start a Linux Docker container mounting the Windows .claude directory:

``
docker run ... -v "%USERPROFILE%\.claude:/home/claude/.claude" -e CLAUDE_CONFIG_DIR=/home/claude/.claude -w /workspace ...
``

  1. Use Claude Code interactively inside the container

Observed behavior

A directory is created in /workspace (the CWD) with the literal name:

C:Usersdvora.claudepluginsmarketplacesclaude-plugins-official

This is clearly the Windows path C:\Users\dvora\.claude\plugins\marketplace\claude-plugins-official with backslashes stripped, interpreted as a relative path on Linux and created as a single directory name.

Expected behavior

Claude Code should resolve plugin/marketplace paths relative to CLAUDE_CONFIG_DIR (or ~/.claude) rather than using a cached absolute Windows path from the config files.

Environment

  • Host: Windows 11
  • Container: Debian Bookworm (Linux)
  • Claude Code: latest (installed via curl -fsSL https://claude.ai/install.sh | bash)
  • Docker mount: %USERPROFILE%\.claude:/home/claude/.claude
  • CLAUDE_CONFIG_DIR=/home/claude/.claude

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗