Add note on WSL2 path formatting for hot reloading in Rancher Desktop on Windows #1769
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
⚡️ Deploying PR Preview... |
Darasimi-Ajewole
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a clarification to the Rancher Desktop documentation for Windows users running LocalStack via WSL2.
Specifically, it documents that when using hot reloading for Lambda functions, paths to Lambda handlers must be specified using WSL2-compatible paths
/mnt/c/rather than Windows-style pathsC:\Without this, volume mounting of the lambda code into the lambda container would fail with a unintelligible error.
Changes:
Added a note under the Windows section of the Rancher Desktop guide.
Included a code snippet showing the correct WSL2 path format.
Motivation:
Hot reloading is a key developer feature in LocalStack, and ensuring it works reliably in WSL2-based workflows improves developer experience and reduces setup friction.