Fix bind mount source for Windows hosts where HOME is unset #2
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TJC/devcontainer-features!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-windows-home-mount"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
On Windows, ${localEnv:HOME} expands to an empty string in devcontainer-feature.json (Windows uses USERPROFILE, not HOME), causing the bind mount source to resolve to a literal "/.claude/.credentials.json" and fail with "bind source path does not exist". Concatenate both vars so exactly one wins on each platform: ${localEnv:HOME}${localEnv:USERPROFILE}.
Add a lint script that asserts every mount source mentioning HOME also mentions USERPROFILE, and wire it into the test workflow so the regression can't sneak back in.