/var/task is owned by aws_user:1000 now, but lambci/lambda:build-provided.al2 runs as sbx_user1051, which makes sls offline start die with permission errors like not being able to access /var/task.
sls offline is tested in the integration test (integration-test/run.sh), and that currently passes - are you able to modify it to show what's failing for you?
/var/task
is owned byaws_user:1000
now, butlambci/lambda:build-provided.al2
runs assbx_user1051
, which makessls offline start
die with permission errors like not being able to access/var/task
.How can this be rectified?
Using sls yaml config:
Ta!