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 #1079

Open
mtmeyer opened this issue Sep 16, 2024 · 2 comments · May be fixed by #1082
Open

Python function container build targets wrong architecture #1079

mtmeyer opened this issue Sep 16, 2024 · 2 comments · May be fixed by #1082
Assignees
Labels
help wanted Extra attention is needed

Comments

@mtmeyer
Copy link

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.

@mtmeyer mtmeyer linked a pull request Sep 17, 2024 that will close this issue
@thdxr thdxr self-assigned this Sep 23, 2024
@toughrogrammer
Copy link

it's really critical to deploy python lambda.

@jayair jayair added the help wanted Extra attention is needed label Sep 27, 2024
@mtmeyer
Copy link
Author

mtmeyer commented Sep 28, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants