aws-sam-cli: Debugging .Net Core with SAM Local not working

Description

I’m trying to debug sam-app DotNetCore 2.1 Hello World application on my environment, but couldn’t get it attached.

Steps to reproduce

I’ve followed these steps: https://github.com/awslabs/aws-sam-cli/blob/develop/docs/usage.md#debugging-net-core-21--20-functions

Got the application by executing sam init --runtime dotnetcore2.1

Then I did:

1. Using PowerShell: .\build.ps1 --target=Package --configuration=Debug
2. Using command: docker run --rm --mount type=bind,src=e:/tools/vsdbg,dst=/vsdbg --entrypoint bash lambci/lambda:dotnetcore2.1 -c “curl -sSL https://aka.ms/getvsdbgsh | bash /dev/stdin -v latest -l /vsdbg”
3. On VS Code, I amended the launch.json with:

{ “name”: “.NET Core Docker Attach”, “type”: “coreclr”, “request”: “attach”, “processId”: “1”,

“pipeTransport”: { “pipeProgram”: “sh”, “pipeArgs”: [ “-c”, “docker exec -i $(docker ps -q -f publish=5858) ${debuggerCommand}” ], “debuggerPath”: “/tmp/lambci_debug_files/vsdbg”, “pipeCwd”: “${workspaceFolder}”, },

“windows”: { “pipeTransport”: { “pipeProgram”: “powershell”, “pipeArgs”: [ “-c”, “docker exec -i $(docker ps -q -f publish=5858) ${debuggerCommand}” ], “debuggerPath”: “/tmp/lambci_debug_files/vsdbg”, “pipeCwd”: “${workspaceFolder}”, } },

1. Using command: sam local start-api -d 5858 --debugger-path e:/tools/vsdbg --profile personal
2. Using postmand: GET http://127.0.0.1:3000/hello
3. I could notice SAM Local executing giving “Waiting for the debugger to attach…”
4. I put a breakpoint on: HelloWorld.Function.FunctionHandler:line 37
5. I started VS Code debugger on “.NET Core Docker Attach”

Observed result

Nothing happens… After sometime I got a “Timeout. Proceeding without debugger.” and code executes without debugging.

SAM Local:

E:\Personal\sam-app-dynamodb\sam-app>sam local start-api -d 5858 --debugger-path e:/tools/vsdbg --profile personal --debug 2019-01-16 13:03:28 Using SAM Template at E:\Personal\sam-app-dynamodb\sam-app\template.yaml 2019-01-16 13:03:28 Changing event name from creating-client-class.iot-data to creating-client-class.iot-data-plane 2019-01-16 13:03:28 Changing event name from before-call.apigateway to before-call.api-gateway 2019-01-16 13:03:28 Changing event name from request-created.machinelearning.Predict to request-created.machine-learning.Predict 2019-01-16 13:03:28 Changing event name from before-parameter-build.autoscaling.CreateLaunchConfiguration to before-parameter-build.auto-scaling.CreateLaunchConfiguration 2019-01-16 13:03:28 Changing event name from before-parameter-build.route53 to before-parameter-build.route-53 2019-01-16 13:03:28 Changing event name from request-created.cloudsearchdomain.Search to request-created.cloudsearch-domain.Search 2019-01-16 13:03:28 Changing event name from docs..autoscaling.CreateLaunchConfiguration.complete-section to docs..auto-scaling.CreateLaunchConfiguration.complete-section 2019-01-16 13:03:28 Changing event name from before-parameter-build.logs.CreateExportTask to before-parameter-build.cloudwatch-logs.CreateExportTask 2019-01-16 13:03:28 Changing event name from docs..logs.CreateExportTask.complete-section to docs..cloudwatch-logs.CreateExportTask.complete-section 2019-01-16 13:03:28 Changing event name from before-parameter-build.cloudsearchdomain.Search to before-parameter-build.cloudsearch-domain.Search 2019-01-16 13:03:28 Changing event name from docs..cloudsearchdomain.Search.complete-section to docs..cloudsearch-domain.Search.complete-section 2019-01-16 13:03:28 Setting config variable for profile to ‘personal’ 2019-01-16 13:03:28 local start-api command is called 2019-01-16 13:03:28 Skipping environment variable credential check because profile name was explicitly set. 2019-01-16 13:03:28 Looking for credentials via: assume-role 2019-01-16 13:03:28 Looking for credentials via: shared-credentials-file 2019-01-16 13:03:28 Found credentials in shared credentials file: ~/.aws/credentials 2019-01-16 13:03:28 Loading JSON file: C:\Program Files\Amazon\AWSSAMCLI\runtime\lib\site-packages\botocore\data\endpoints.json 2019-01-16 13:03:28 Event choose-service-name: calling handler <function handle_service_name_alias at 0x00000229D8BEE6A8> 2019-01-16 13:03:28 Loading JSON file: C:\Program Files\Amazon\AWSSAMCLI\runtime\lib\site-packages\botocore\data\serverlessrepo\2017-09-08\service-2.json 2019-01-16 13:03:28 Event creating-client-class.serverlessapplicationrepository: calling handler <function add_generate_presigned_url at 0x00000229D8C2CD08> 2019-01-16 13:03:28 The s3 config key is not a dictionary type, ignoring its value of: None 2019-01-16 13:03:28 Setting serverlessrepo timeout as (60, 60) 2019-01-16 13:03:28 Loading JSON file: C:\Program Files\Amazon\AWSSAMCLI\runtime\lib\site-packages\botocore\data_retry.json 2019-01-16 13:03:28 Registering retry handlers for service: serverlessrepo 2019-01-16 13:03:28 No Parameters detected in the template 2019-01-16 13:03:28 2 resources found in the template 2019-01-16 13:03:28 Found Serverless function with name=‘HelloWorldFunction’ and CodeUri=‘./artifacts/HelloWorld.zip’ 2019-01-16 13:03:28 Trying paths: [‘C:\Users\MatheusMaximodeArauj\.docker\config.json’, ‘C:\Users\MatheusMaximodeArauj\.dockercfg’] 2019-01-16 13:03:28 Found file at path: C:\Users\MatheusMaximodeArauj.docker\config.json 2019-01-16 13:03:28 Found ‘auths’ section 2019-01-16 13:03:28 Auth data for https://index.docker.io/v1/ is absent. Client might be using a credentials store instead. 2019-01-16 13:03:28 Found ‘credsStore’ section 2019-01-16 13:03:28 http://localhost:None “GET /v1.35/_ping HTTP/1.1” 200 2 2019-01-16 13:03:28 Event choose-service-name: calling handler <function handle_service_name_alias at 0x00000229D8BEE6A8> 2019-01-16 13:03:28 Event creating-client-class.serverlessapplicationrepository: calling handler <function add_generate_presigned_url at 0x00000229D8C2CD08> 2019-01-16 13:03:28 The s3 config key is not a dictionary type, ignoring its value of: None 2019-01-16 13:03:28 Setting serverlessrepo timeout as (60, 60) 2019-01-16 13:03:28 Registering retry handlers for service: serverlessrepo 2019-01-16 13:03:28 No Parameters detected in the template 2019-01-16 13:03:28 2 resources found in the template 2019-01-16 13:03:28 Found ‘1’ API Events in Serverless function with name ‘HelloWorldFunction’ 2019-01-16 13:03:28 Detected Inline Swagger definition 2019-01-16 13:03:28 Lambda function integration not found in Swagger document at path=‘/hello’ method=‘get’ 2019-01-16 13:03:28 Found ‘0’ APIs in resource ‘ServerlessRestApi’ 2019-01-16 13:03:28 Removed duplicates from ‘0’ Explicit APIs and ‘1’ Implicit APIs to produce ‘1’ APIs 2019-01-16 13:03:28 1 APIs found in the template 2019-01-16 13:03:28 Event choose-service-name: calling handler <function handle_service_name_alias at 0x00000229D8BEE6A8> 2019-01-16 13:03:28 Loading JSON file: C:\Program Files\Amazon\AWSSAMCLI\runtime\lib\site-packages\botocore\data\lambda\2015-03-31\service-2.json 2019-01-16 13:03:28 Event creating-client-class.lambda: calling handler <function add_generate_presigned_url at 0x00000229D8C2CD08> 2019-01-16 13:03:28 The s3 config key is not a dictionary type, ignoring its value of: None 2019-01-16 13:03:28 Setting lambda timeout as (60, 60) 2019-01-16 13:03:28 Registering retry handlers for service: lambda 2019-01-16 13:03:28 Trying paths: [‘C:\Users\MatheusMaximodeArauj\.docker\config.json’, ‘C:\Users\MatheusMaximodeArauj\.dockercfg’] 2019-01-16 13:03:28 Found file at path: C:\Users\MatheusMaximodeArauj.docker\config.json 2019-01-16 13:03:28 Found ‘auths’ section 2019-01-16 13:03:28 Auth data for https://index.docker.io/v1/ is absent. Client might be using a credentials store instead. 2019-01-16 13:03:28 Found ‘credsStore’ section 2019-01-16 13:03:28 Mounting HelloWorldFunction at http://127.0.0.1:3000/hello [GET] 2019-01-16 13:03:28 You can now browse to the above endpoints to invoke your functions. You do not need to restart/reload SAM CLI while working on your functions changes will be reflected instantly/automatically. You only need to restart SAM CLI if you update your AWS SAM template 2019-01-16 13:03:28 Localhost server is starting up. Multi-threading = False 2019-01-16 13:03:28 * Running on http://127.0.0.1:3000/ (Press CTRL+C to quit) 2019-01-16 13:03:50 Constructed String representation of Event to invoke Lambda. Event: {“httpMethod”: “GET”, “body”: null, “resource”: “/hello”, “requestContext”: {“resourceId”: “123456”, “apiId”: “1234567890”, “resourcePath”: “/hello”, “httpMethod”: “GET”, “requestId”: “c6af9ac6-7b61-11e6-9a41-93e8deadbeef”, “accountId”: “123456789012”, “stage”: “prod”, “identity”: {“apiKey”: null, “userArn”: null, “cognitoAuthenticationType”: null, “caller”: null, “userAgent”: “Custom User Agent String”, “user”: null, “cognitoIdentityPoolId”: null, “cognitoAuthenticationProvider”: null, “sourceIp”: “127.0.0.1”, “accountId”: null}, “extendedRequestId”: null, “path”: “/hello”}, “queryStringParameters”: null, “headers”: {“Cache-Control”: “no-cache”, “Postman-Token”: “e261198c-ad7c-4909-93ca-c16d33953f1f”, “User-Agent”: “PostmanRuntime/7.6.0”, “Accept”: “/”, “Host”: “127.0.0.1:3000”, “Accept-Encoding”: “gzip, deflate”, “Connection”: “keep-alive”, “X-Forwarded-Proto”: “http”, “X-Forwarded-Port”: “3000”}, “pathParameters”: null, “stageVariables”: null, “path”: “/hello”, “isBase64Encoded”: false} 2019-01-16 13:03:50 Found one Lambda function with name ‘HelloWorldFunction’ 2019-01-16 13:03:50 Invoking HelloWorld::HelloWorld.Function::FunctionHandler (dotnetcore2.1) 2019-01-16 13:03:50 Environment variables overrides data is standard format 2019-01-16 13:03:50 Loading AWS credentials from session with profile ‘personal’ 2019-01-16 13:03:50 Resolving code path. Cwd=E:\Personal\sam-app-dynamodb\sam-app, CodeUri=./artifacts/HelloWorld.zip 2019-01-16 13:03:50 Resolved absolute path to code is E:\Personal\sam-app-dynamodb\sam-app\artifacts\HelloWorld.zip 2019-01-16 13:03:50 Decompressing E:\Personal\sam-app-dynamodb\sam-app\artifacts\HelloWorld.zip 2019-01-16 13:03:50 File Amazon.Lambda.APIGatewayEvents.dll in zipfile does not have permission information 2019-01-16 13:03:50 File Amazon.Lambda.Core.dll in zipfile does not have permission information 2019-01-16 13:03:50 File Amazon.Lambda.Serialization.Json.dll in zipfile does not have permission information 2019-01-16 13:03:50 File HelloWorld.deps.json in zipfile does not have permission information 2019-01-16 13:03:50 File HelloWorld.dll in zipfile does not have permission information 2019-01-16 13:03:50 File HelloWorld.pdb in zipfile does not have permission information 2019-01-16 13:03:50 File HelloWorld.runtimeconfig.json in zipfile does not have permission information 2019-01-16 13:03:50 File Newtonsoft.Json.dll in zipfile does not have permission information 2019-01-16 13:03:50 Skipping building an image since no layers were defined 2019-01-16 13:03:50 Trying paths: [‘C:\Users\MatheusMaximodeArauj\.docker\config.json’, ‘C:\Users\MatheusMaximodeArauj\.dockercfg’] 2019-01-16 13:03:50 Found file at path: C:\Users\MatheusMaximodeArauj.docker\config.json 2019-01-16 13:03:50 Found ‘auths’ section 2019-01-16 13:03:50 Auth data for https://index.docker.io/v1/ is absent. Client might be using a credentials store instead. 2019-01-16 13:03:50 Found ‘credsStore’ section 2019-01-16 13:03:50 http://localhost:None “GET /v1.35/images/lambci/lambda:dotnetcore2.1/json HTTP/1.1” 200 None 2019-01-16 13:03:50 Looking for auth config 2019-01-16 13:03:50 Using credentials store “wincred” 2019-01-16 13:03:50 Looking for auth entry for ‘https://index.docker.io/v1/’ 2019-01-16 13:03:50 Found auth config 2019-01-16 13:03:52 http://localhost:None “POST /v1.35/images/create?tag=dotnetcore2.1&fromImage=lambci%2Flambda HTTP/1.1” 200 None

Fetching lambci/lambda:dotnetcore2.1 Docker container image… 2019-01-16 13:03:52 Mounting C:\Users\MATHEU~1\AppData\Local\Temp\tmpi6ckro33 as /var/task:ro inside runtime container 2019-01-16 13:03:52 http://localhost:None “POST /v1.35/containers/create HTTP/1.1” 201 90 2019-01-16 13:03:52 http://localhost:None “GET /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/json HTTP/1.1” 200 None 2019-01-16 13:03:52 http://localhost:None “GET /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/json HTTP/1.1” 200 None 2019-01-16 13:03:53 http://localhost:None “POST /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/start HTTP/1.1” 204 0 2019-01-16 13:03:53 Setting up SIGTERM interrupt handler 2019-01-16 13:03:53 http://localhost:None “GET /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/json HTTP/1.1” 200 None 2019-01-16 13:03:53 http://localhost:None “POST /containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/attach?stdout=1&stderr=1&logs=1&stream=1&stdin=0 HTTP/1.1” 101 0 Waiting for the debugger to attach… Timeout. Proceeding without debugger. START RequestId: d70ef1ca-a936-4917-8ab6-06495f4d1a5c Version: $LATEST END RequestId: d70ef1ca-a936-4917-8ab6-06495f4d1a5c REPORT RequestId d70ef1ca-a936-4917-8ab6-06495f4d1a5c Duration: 867 ms Billed Duration: 900 ms Memory Size 128 MB Max Memory Used: 46 MB 2019-01-16 13:13:55 http://localhost:None “GET /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179/json HTTP/1.1” 200 None 2019-01-16 13:13:55 http://localhost:None “DELETE /v1.35/containers/11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179?v=False&link=False&force=True HTTP/1.1” 204 0 2019-01-16 13:13:55 127.0.0.1 - - [16/Jan/2019 13:13:55] “GET /hello HTTP/1.1” 200 -

Docker events:

2019-01-16T13:03:52.306960600Z image pull lambci/lambda:dotnetcore2.1 (name=lambci/lambda) 2019-01-16T13:03:52.433924100Z container create 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:03:52.622378700Z network connect 2531e757c1db9739e2fa4961ac98568013a9b64381c5fec7f13274e4ac21a69d (container=11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179, name=bridge, type=bridge) 2019-01-16T13:03:53.154367200Z container start 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:03:53.179674800Z container attach 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:04:14.174976200Z container exec_create: /tmp/lambci_debug_files/vsdbg --interpreter=vscode 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (execID=ce4932666f344ad3c14acc4feef2407b4e83ef8696a9b8ff7c5682bc0505d2d8, image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:04:14.180179100Z container exec_start: /tmp/lambci_debug_files/vsdbg --interpreter=vscode 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (execID=ce4932666f344ad3c14acc4feef2407b4e83ef8696a9b8ff7c5682bc0505d2d8, image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:13:54.278192500Z container exec_die 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (execID=ce4932666f344ad3c14acc4feef2407b4e83ef8696a9b8ff7c5682bc0505d2d8, exitCode=137, image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:13:54.434456200Z container die 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (exitCode=0, image=lambci/lambda:dotnetcore2.1, name=stoic_robinson) 2019-01-16T13:13:54.909337100Z network disconnect 2531e757c1db9739e2fa4961ac98568013a9b64381c5fec7f13274e4ac21a69d (container=11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179, name=bridge, type=bridge) 2019-01-16T13:13:55.043738200Z container destroy 11be84ca7cf298e064fb093ddb5dca58f16dfb3c1f66e70ce731ae6fd902f179 (image=lambci/lambda:dotnetcore2.1, name=stoic_robinson)

Expected result

I was expecting my breakpoint to be hit by execution code.

Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS Name: Microsoft Windows 10 Pro OS Version: 10.0.17763 N/A Build 17763

DotNet Core SDK Version: 2.1.503

AWS CLI Version: aws-cli/1.16.69 Python/3.6.0 Windows/10 botocore/1.12.59

SAM Version: SAM CLI, version 0.10.0

Docker version 18.09.1, build 4c52b90

Add --debug flag to command you are running