Skip to content

Add note on WSL2 path formatting for hot reloading in Rancher Desktop on Windows #1769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions content/en/user-guide/lambda-tools/hot-reloading/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,17 @@ Therefore, filesystem changes persist between code changes for invocations dispa
If using Docker Desktop on macOS, you might need to allow [file sharing](https://docs.docker.com/desktop/settings/mac/#file-sharing) for your target folders.
MacOS may prompt you to grant Docker access to your target folders.

**WSL2-compatible paths required with Rancher Desktop on Windows:**
Make sure your Lambda handler paths are specified using WSL2-compatible paths. For example, instead of using a Windows-style path like:
```bash
C:\Users\myuser\projects\lambda\handler.py
```
Use the corresponding WSL-style path:
```bash
/mnt/c/Users/myuser/projects/lambda/handler.py
```
This ensures that LocalStack can properly mount and watch your Lambda code inside the container when running under WSL2.

**Layer limit with hot reloading for layers:**
When hot reloading is active for a Lambda layer (Pro), the function can use at most one layer.

Expand Down