LocalStack integration with Pro

0 tests   - 1 827   0 ✔️  - 1 481   0s ⏱️ - 1h 4m 39s
0 suites  -        1   0 💤  -    345 
0 files    -        1   0 ❌  -        1 

Results for commit 085d93c. ± Comparison against base commit fad6714.

♻️ This comment has been updated with latest results.

I was linked to this PR from this Slack thread, and I wanted to drop a quick note about user settings. From what I have gathered, primarily from the Bref project, AWS Lambda executes code with nobody:nobody user/group.

This does not seem to be the case with Localstack Lambda, because when I try to execute my functions (with the PHP-FPM layer from Bref) they fail saying that "no user is defined". The error happens in the PHP-FPM layer, but the exact same layer has no issues in AWS proper. After discussing this with the Bref community, it seems this error will only happen when the Lambda environment executes as someone other than nobody.

If nothing else, it would be helpful to have LAMBDA_DOCKER_FLAGS support the --user flag, which it currently does not.

thanks Woody @shadowhand, this is helpful feedback we'll consider!

@shadowhand Thank you for reporting your findings 🙏 I created a separate issue to track the progress on this lambda runtime parity issue #7722

I was linked to this PR from this Slack thread, and I wanted to drop a quick note about user settings. From what I have gathered, primarily from the Bref project, AWS Lambda executes code with nobody:nobody user/group.

This does not seem to be the case with Localstack Lambda, because when I try to execute my functions (with the PHP-FPM layer from Bref) they fail saying that "no user is defined". The error happens in the PHP-FPM layer, but the exact same layer has no issues in AWS proper. After discussing this with the Bref community, it seems this error will only happen when the Lambda environment executes as someone other than nobody.

If nothing else, it would be helpful to have LAMBDA_DOCKER_FLAGS support the --user flag, which it currently does not.

Your suggested workaround is now supported and mentioned here: #7722 (comment)
This enables running PHP/Bref applications on LocalStack.