Closed ChronosMasterOfAllTime closed 1 week ago
It seems this issue was attempted to be fixed in #7061, however the issue still persists
Docker 4.33 seems to have caused this issue, downgrading to 4.32 fixed it for now. Can you please look into why?
As discussed in the previous issue, this is not originating from SAM CLI, but it is coming from Docker Desktop. What happens if you try to build with SAM_BUILD_MODE=debug sam build
, can you do sam local invoke
? (Please remember to rebuild without SAM_BUILD_MODE=debug
before you actually deploy your function)
As discussed in the previous issue, this is not originating from SAM CLI, but it is coming from Docker Desktop. What happens if you try to build with
SAM_BUILD_MODE=debug sam build
, can you dosam local invoke
? (Please remember to rebuild withoutSAM_BUILD_MODE=debug
before you actually deploy your function)
I tried that approach and it still didn't work. Cleared my entire docker cache to ensure a "fresh start".
Just to confirm you are using a Rust lambda function right?
Docker 4.33 seems to have caused this issue, downgrading to 4.32 fixed it for now.
In this case, I will recommend creating an issue on https://github.com/docker/for-mac/issues for Docker Desktop to track this issue.
Experiencing this with a golang lambda as well on v4.33
Just to confirm you are using a Rust lambda function right?
Docker 4.33 seems to have caused this issue, downgrading to 4.32 fixed it for now.
In this case, I will recommend creating an issue on https://github.com/docker/for-mac/issues for Docker Desktop to track this issue.
I am running the golang compiled binary on the bootstrap provided.al2023 image as go1.x is deprecated
Yeah I opened an issue in a couple places. It's either an image issue or docker 4.33 issue
Thanks for opening the other issues. Since it works with earlier docker version, I suspect it is related to latest Docker release.
I will keep this open for now for visibility, until we get some updates from the other issues above.
Fixed in docker 4.34.0
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description:
when trying to run a lambda (either through
sam local invoke
orsam local start-api
Any invocation of the image is met with the following error
Init failed error=fork/exec /var/task/bootstrap: invalid argument InvokeID=
Steps to reproduce:
Install AWS-SAM-CLI 1.121.0 Install Docker 4.33
Try to execute a lambda using the
provided.al2
imageExpectation: Execution succeeds
Actual:
Init failed error=fork/exec /var/task/bootstrap: invalid argument InvokeID=
Observed result:
Expected result:
Lambda execution successful, but it isn't.
Execution succeeds with Docker v4.32.0
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
MacOs x86
sam --version
: 1.121.0Add --debug flag to command you are running