-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SAM doesn't work with Rancher Desktop #3715
Comments
SAM CLI does not support Rancher Desktop at the moment. Please see #3595 where we are looking at options other than Docker. Closing as dup. |
Because this comes up as the first result when Googling "aws sam rancher", this is the relevant comment from the thread mentioned above:
Maybe the sam cli could be updated to provide a more helpful response to
|
Hey 👋
Edit: |
Description:
I'm trying to move away from Docker Desktop and am trying Rancher Desktop instead. The SAM CLI reports
no response from invoke container for <function-name>
when tryingsam local invoke
. Note: standarddocker
commands seem to run fine (Rancher symlinksdocker
into/usr/local/bin
). It may be worth mentioning that Rancher Desktop uses QEMU in the backend, via Lima.Steps to reproduce:
aws-sam-cli
sam local invoke
for any lambda projectObserved result:
Expected result:
Some kind of output from the lambda.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.40.1The text was updated successfully, but these errors were encountered: