SAM Build Not Mounting Lambda Code in `/var/task` During `sam local start api` on Windows

[pedrocimp]

Description:

When using npm run build and running sam local start api or sam local invoke, SAM builds the Lambda image on the fly. However, it seems that the Lambda code is not being mounted correctly in /var/task, which results in an empty directory. This prevents the Lambda from executing properly.

Context:

I expect SAM to mount the built Lambda sources from dist/ into /var/task inside the container. However, the /var/task directory is empty, making it impossible to execute the Lambda function via sam local start api.

I've tried multiple solutions but couldn't resolve this issue. It might be related to switching from a Linux development environment to a Windows environment.

In my template.yml, I point the CodeUri to the compiled code in the dist/ directory, like this:

CodeUri: dist/lambdas/myFunction/

Expected behavior:

The compiled Lambda code should be mounted into /var/task inside the container to allow the Lambda function to execute properly.

Environment:

• Operating System: Windows
• SAM CLI Version: Tested with version 1.120
• Docker Version: 26.1.0-rd
• Docker setup: Running on WSL2
• Custom Lambda Image: Defined in template.yml

Steps to reproduce:

1. Run npm run build. [npx tsc --project tsconfig.build.json]
2. Start the Lambda function using either sam local start api or sam local invoke.
3. Inspect the container, and observe that /var/task is empty.

Possible suggestions or fixes:

• Ensure that SAM properly mounts the Lambda code into the /var/task directory during execution on Windows.
• Investigate if the issue is related to file mounting differences between Linux and Windows.

Thank you for your help!

[aaythapa]

Looks like a SAM CLI issue, transferring over to them

[sidhujus]

Hi thanks for raising this issue! Could you provide the output generated by sam cli when running the commands with the --debug flag?

[pedrocimp]

Command used:

sam local start-api --warm-containers LAZY --host 0.0.0.0 -p 13000 --docker-network my_network --container-host 127.0.0.1 --template template.yml --env-vars tests/resources/environment.json --log-file logs.txt --invoke-image myprivaterepo/public.ecr.aws/lambda/nodejs:20

SAM CLI Output:

2024-09-30 17:03:27,163 | Found one Lambda function with name 'myFunction'
2024-09-30 17:03:27,165 | Invoking index.handler (nodejs20.x)
2024-09-30 17:03:27,167 | Loading AWS credentials from session with profile 'None'
2024-09-30 17:03:27,229 | Resolving code path. Cwd=C:\my\project\path, CodeUri=C:\my\project\path\dist\lambdas\myFunction
2024-09-30 17:03:27,232 | Resolved absolute path to code is C:\my\project\path\dist\lambdas\myFunction
2024-09-30 17:03:27,233 | Resolving code path. Cwd=C:\my\project\path, CodeUri=C:\my\project\path\dist\lambdas\myFunction
2024-09-30 17:03:27,236 | Resolved real code path to C:\my\project\path\dist\lambdas\myFunction
2024-09-30 17:03:27,242 | watch resource C:\my\project\path\dist\lambdas\myFunction
2024-09-30 17:03:27,244 | Create Observer for resource C:\my\project\path\dist\lambdas\myFunction with recursive True
2024-09-30 17:03:27,248 | watch resource C:\my\project\path\dist\lambdas\myFunction's parent C:\my\project\path\dist\lambdas
2024-09-30 17:03:27,250 | Create Observer for resource C:\my\project\path\dist\lambdas with recursive False

2024-09-30 17:03:43,164 | Code C:\my\project\path\dist\lambdas\myFunction is not a zip/jar file
2024-09-30 17:03:44,214 | Local image is up-to-date
Building image.............................
2024-09-30 17:04:53,053 | Checking free port on 127.0.0.1:6502
2024-09-30 17:04:53,072 | Using local image: samcli/lambda-nodejs:20-x86_64-56f48dd3e28f986d7e755f073.

2024-09-30 17:04:53,075 | Mounting C:\my\project\path\dist\lambdas\myFunction as /var/task:ro,delegated, inside runtime container
2024-09-30 17:04:56,623 | Starting a timer for 300 seconds for function 'myFunction'
2024-09-30 17:04:56,627 | Getting lock for the key 127.0.0.1-6502
2024-09-30 17:04:56,629 | Waiting to retrieve the lock (127.0.0.1-6502) to start invocation
2024-09-30 17:04:58,093 | Unable to find Click Context for getting session_id.
2024-09-30 17:04:58 127.0.0.1 - - [30/Sep/2024 17:04:58] "GET /myFunction/{id} HTTP/1.1" 500 -

Inside the container:
bash-5.2# ls /var/task => empty

[pedrocimp]

I don't use sam build for building my project and generating the /dist folder, my project is built with npx tsc --project tsconfig.build.json .
Maybe there is a link with my issue ?
Thanks :)

[pedrocimp]

@aaythapa @sidhujus any news ?

[leonartdoss]

I'm facing the same issue :( Any news on this topic?

[leonartdoss]

I don't use sam build for building my project and generating the /dist folder, my project is built with npx tsc --project tsconfig.build.json . Maybe there is a link with my issue ? Thanks :)

I don't think so because I'm building the project with sam build and it doesn't work.

[clocobhupesh]

did you guys found any solution

[leonartdoss]

did you guys found any solution

No, I changed my approach and now I'm running SAM directly from Windows.