-
Notifications
You must be signed in to change notification settings - Fork 462
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
(Rancher) SAM local invoke failed: Expecting value: line 1 column 1 #3786
Comments
Thanks for the very clear report! Rancher is reported as working with SAM CLI but it requires some setup. Some notes are in #3413 , starting with this comment: #3413 (comment) |
@justinmk3 Thank you for the quick response. I tried the above mentioned resources with no success. I need to add another piece of the puzzle: I get a "Failed to attach debugger" error sometimes: Logs: Failed to attach debugger
|
Looks like I missed a very important detail from aws/aws-sam-cli#3595 (comment):
which are all the command options I need for debugging lambdas locally.
Thank you for the help @justinmk3 |
Troubleshooting steps mentioned in aws/aws-sam-cli#5646 (comment) may be useful:
|
Problem
I am having trouble debugging a lambda locally using sam + aws toolkit + rancher desktop (dockerd). The debugger never makes it to the breakpoint set withing my lambda.
However, when I quit rancher desktop and open docker desktop, not making any changes, the debugger hits the desired breakpoint.
Using rancher desktop due to work constraints.
Steps to reproduce the issue
Use the aws toolkit wizard to create the basic python3.7 (image) HelloWorld lambda, leaving all defaults as is with
rancher desktop 1.9.1
(dockerd).AWS Toolkit logs
.vscode/launch.json
Dockerfile
requirements.txt
template.yaml
Expected behavior
The debugger should stop at the desired breakpoint within the lambda.
System details (run the
AWS: About Toolkit
command)The text was updated successfully, but these errors were encountered: