From d4f02088c25d3258d9bfb23cd487dcd48b215f6c Mon Sep 17 00:00:00 2001 From: eduardo <83775838+drauedo@users.noreply.github.com> Date: Tue, 8 Oct 2024 08:44:54 +0200 Subject: [PATCH] Lambda Hot Reloading not updating function when not using Docker desktop (#1502) Co-authored-by: MarcelStranak --- .../en/user-guide/lambda-tools/hot-reloading/index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/en/user-guide/lambda-tools/hot-reloading/index.md b/content/en/user-guide/lambda-tools/hot-reloading/index.md index 5152ce4b0a..7e9bff8005 100644 --- a/content/en/user-guide/lambda-tools/hot-reloading/index.md +++ b/content/en/user-guide/lambda-tools/hot-reloading/index.md @@ -42,6 +42,16 @@ MacOS may prompt you to grant Docker access to your target folders. **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. +{{< callout >}} +Configuring the file sharing mechanism in Rancher Desktop or Colima distributions is necessary to enable hot reloading for Lambda. + +* For Rancher Desktop it is required to set the configuration `LAMBDA_DOCKER_FLAGS=-e LOCALSTACK_FILE_WATCHER_STRATEGY=polling`. +* For Colima, it is required to start with the Virtiofs mount type: `colima start --vm-type vz --mount-type virtiofs`. + +More information about this behavior can be found in the following [GitHub issue.](https://github.com/localstack/localstack/issues/11415#issuecomment-2341140998) + +{{< /callout >}} + ## Application Configuration Examples ### Hot reloading for JVM Lambdas