Skip to content
This repository was archived by the owner on Jul 9, 2025. It is now read-only.

Commit d4f0208

Browse files
Lambda Hot Reloading not updating function when not using Docker desktop (#1502)
Co-authored-by: MarcelStranak <marcel.stranak@localstack.cloud>
1 parent e6e9b26 commit d4f0208

File tree

1 file changed

+10
-0
lines changed
  • content/en/user-guide/lambda-tools/hot-reloading

1 file changed

+10
-0
lines changed

content/en/user-guide/lambda-tools/hot-reloading/index.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,16 @@ MacOS may prompt you to grant Docker access to your target folders.
4242
**Layer limit with hot reloading for layers:**
4343
When hot reloading is active for a Lambda layer (Pro), the function can use at most one layer.
4444

45+
{{< callout >}}
46+
Configuring the file sharing mechanism in Rancher Desktop or Colima distributions is necessary to enable hot reloading for Lambda.
47+
48+
* For Rancher Desktop it is required to set the configuration `LAMBDA_DOCKER_FLAGS=-e LOCALSTACK_FILE_WATCHER_STRATEGY=polling`.
49+
* For Colima, it is required to start with the Virtiofs mount type: `colima start --vm-type vz --mount-type virtiofs`.
50+
51+
More information about this behavior can be found in the following [GitHub issue.](https://github.com/localstack/localstack/issues/11415#issuecomment-2341140998)
52+
53+
{{< /callout >}}
54+
4555
## Application Configuration Examples
4656

4757
### Hot reloading for JVM Lambdas

0 commit comments

Comments
 (0)