Error when deploying docker image on lambda using SAM instead of serverless

[hafsalmetvr]

Hi @mnapoli

I am running a Laravel application using docker and tried to deploy it in lambda using bref and SAM

Dockerfile

FROM bref/php-81-fpm
RUN curl -s https://getcomposer.org/installer | php
RUN php composer.phar require bref/bref
COPY . /var/task
CMD _HANDLER=index.php /opt/bootstrap

and i did sam build and sam deploy -g

but it shows error like "entrypoint requires the handler name to be the first argument
when i change Dockerfile like

FROM bref/php-81-fpm
RUN curl -s https://getcomposer.org/installer | php
RUN php composer.phar require bref/bref
COPY . /var/task
CMD ["public/index.php"]

it returns error like Fatal error: Uncaught Error: Class "Bref\Runtime\LambdaRuntime" not found in /var/runtime/bootstrap:28

and my template.yaml is like

AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
  ociphp2
  Sample SAM Template for php oci

Globals:
  Function:
    Timeout: 3

Resources:
  LaravelTest:
    Type: AWS::Serverless::Function
    Properties:
      PackageType: Image
      Events:
        DynamicRequestsRoot:
          Type: HttpApi
          Properties:
            Path: /
            Method: ANY
        DynamicRequestsProxy:
          Type: HttpApi
          Properties:
            Path: /{proxy+}
            Method: ANY
    Metadata:
      DockerTag: laratest
      DockerContext: ./
      Dockerfile: Dockerfile

Outputs:
  LaravelTest:
    Description: "API Gateway endpoint URL for Prod stage for LaravelAPI"
    Value: !Sub "https://${ServerlessHttpApi}.execute-api.${AWS::Region}.amazonaws.com/"

Actually i was successfully deploy and run application in lambda using serverless framework (serverless.yml), but now i am facing issue while i tried same with AWS SAM

Any help would be appreciated. Thanks

[mnapoli]

Follow the format described in the documentation: https://bref.sh/docs/web-apps/docker.html

Your second attempt looks correct (at least it matches the documentation), but maybe the whole vendor folder is overridden by your COPY . /var/task ?

I would try to run bash in the container and check the content of /var/task.

[hafsalmetvr]

Thank you @mnapoli for your quick reply, let me check it

[hafsalmetvr]

@mnapoli I think you are right, it might be override by Laravel vendor directory.

So i tried to install bref package directly in Laravel project and now i got different error

"errorType": "Bref\\Event\\Http\\FastCgi\\Timeout",
    "errorMessage": "The request timed out after 1985 ms. Note: that duration may be lower than the Lambda timeout, don't be surprised, that is intentional. Indeed, Bref stops the PHP-FPM request *before* a hard Lambda timeout, because a hard timeout prevents all logs to be written to CloudWatch.",
    "stack": [
        "#0 /var/task/vendor/bref/bref/src/Event/Http/HttpHandler.php(25): Bref\\Event\\Http\\FpmHandler->handleRequest()",
        "#1 /var/task/vendor/bref/bref/src/Runtime/Invoker.php(29): Bref\\Event\\Http\\HttpHandler->handle()",
        "#2 /var/task/vendor/bref/bref/src/Runtime/LambdaRuntime.php(91): Bref\\Runtime\\Invoker->invoke()",
        "#3 /var/runtime/bootstrap(43): Bref\\Runtime\\LambdaRuntime->processNextEvent()",
        "#4 {main}"
    ]

[hafsalmetvr]

@mnapoli

it seems like error is happening in Laravel, but its not showing full log in Cloudwatch due to some timeout issue i think
It seems like control is reaching at Laravel's index.php file and i can print anything there and it is displaying when accessing url

i tried "bref/bref": "dev-timeouts-fpm", to see if it helps to see real error

[hafsalmetvr]

file_put_contents(/var/task/storage/framework/views/9412f2b4d69fdcd278d908bf2c307078cbf78812.php): Failed to open stream: Read-only file system {"exception":"[object] (ErrorException(code: 0): file_put_contents(/var/task/storage/framework/views/9412f2b4d69fdcd278d908bf2c307078cbf78812.php): Failed to open stream: Read-only file system at /var/task/vendor/laravel/framework/src/Illuminate/Filesystem/Filesystem.php:187)

I found original error after setting a timeout in template.yaml file

And above it error is fixed by setting
VIEW_COMPILED_PATH=/tmp/storage/framework/views

Finally all the issues are solved and everything working