Skip to content
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

Python function container build targets wrong architecture #4115

Closed
mtmeyer opened this issue Sep 16, 2024 · 2 comments · Fixed by sst/ion#1082
Closed

Python function container build targets wrong architecture #4115

mtmeyer opened this issue Sep 16, 2024 · 2 comments · Fixed by sst/ion#1082
Assignees

Comments

@mtmeyer
Copy link
Contributor

mtmeyer commented Sep 16, 2024

When you run sst deploy from your local machine, Docker seems to build for your local machine rather than the architecture of the target lambda function. I'm running an M1 Macbook and when I deployed the Lambda with sst deploy it resulted in the lambda not being able to be run.
When the same code was deployed from a machine with the same architecture as the lambda, the lambda worked as expected.

{
    live: false,
    handler: "someHandler/main.handler",
    runtime: "python3.11",
    python: {
      container: true
    }
}

Maybe an additional flag needs to be passed to docker to ensure its built with the same architecture as the lambda.

@toughrogrammer
Copy link

it's really critical to deploy python lambda.

@mtmeyer
Copy link
Contributor Author

mtmeyer commented Sep 28, 2024

@toughrogrammer This issue will be resolved with sst/ion#1082 once the SST guys have had a chance to review

@thdxr thdxr transferred this issue from sst/ion Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants