502 error developing with Docker locally #1806

mattspringbett · 2024-05-11T19:30:57Z

mattspringbett
May 11, 2024

I am trying to create a very basic local Docker development environment following the instructions here https://bref.sh/docs/local-development

Here are my files

docker-compose.yml

version: "3.5"
 
services:
    app:
        image: bref/php-82-fpm-dev:2
        ports: [ '8000:8000' ]
        volumes:
            - .:/var/task
        environment:
            HANDLER: public/index.php
            # Assets will be served from this directory
            DOCUMENT_ROOT: public

public/index.php

<?php

echo 'hello world';

?>

composer.json

{
    "require": {
        "bref/bref": "^2.1"
    }
}

The container starts fine (although the handler seems to be empty?)

 ✔ Container app-app-1  Created                                                                                                                                                          0.0s 
Attaching to app-1
app-1  | 11 May 2024 19:20:39,474 [INFO] (rapid) exec '/var/runtime/bootstrap' (cwd=/var/task, handler=)
app-1  | ⚡️ Server is running at http://localhost:8000

Making a request in the browser to localhost:8000 returns the following output in the browser

{"name":"502","$fault":"client","$metadata":{"httpStatusCode":502,"attempts":3,"totalRetryDelay":105},"message":"UnknownError"}

The docker log then contains the following after the request in the browser

app-1  | START RequestId: b955c42f-f0b0-4055-b7c0-26b63f5dbf67 Version: $LATEST
app-1  | 11 May 2024 19:26:59,125 [INFO] (rapid) INIT START(type: on-demand, phase: invoke)
app-1  | 11 May 2024 19:26:59,126 [INFO] (rapid) The extension's directory "/opt/extensions" does not exist, assuming no extensions to be loaded.
app-1  | 11 May 2024 19:26:59,127 [INFO] (rapid) Starting runtime without AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN , Expected?: false
app-1  | 11 May 2024 19:26:59,158 [WARNING] (rapid) First fatal error stored in appctx: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,158 [WARNING] (rapid) Process runtime-14 exited: exit status 255
app-1  | 11 May 2024 19:26:59,158 [INFO] (rapid) INIT RTDONE(status: error)
app-1  | 11 May 2024 19:26:59,158 [INFO] (rapid) INIT REPORT(durationMs: 33.413000)
app-1  | 11 May 2024 19:26:59,158 [INFO] (rapid) INVOKE START(requestId: 75c851e0-8134-4384-809b-7126d3051295)
app-1  | 11 May 2024 19:26:59,158 [ERROR] (rapid) Invoke failed error=Runtime exited with error: exit status 255 InvokeID=75c851e0-8134-4384-809b-7126d3051295
app-1  | 11 May 2024 19:26:59,158 [ERROR] (rapid) Invoke DONE failed: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,158 [WARNING] (rapid) Reset initiated: ReleaseFail
app-1  | 11 May 2024 19:26:59,158 [INFO] (rapid) Waiting for runtime domain processes termination
app-1  | START RequestId: 78a61fe8-90e7-4caf-ae2f-8db30ad1e64f Version: $LATEST
app-1  | 11 May 2024 19:26:59,262 [INFO] (rapid) INIT START(type: on-demand, phase: invoke)
app-1  | 11 May 2024 19:26:59,262 [INFO] (rapid) The extension's directory "/opt/extensions" does not exist, assuming no extensions to be loaded.
app-1  | 11 May 2024 19:26:59,262 [INFO] (rapid) Starting runtime without AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN , Expected?: false
app-1  | 11 May 2024 19:26:59,290 [WARNING] (rapid) First fatal error stored in appctx: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,290 [WARNING] (rapid) Process runtime-16 exited: exit status 255
app-1  | 11 May 2024 19:26:59,290 [INFO] (rapid) INIT RTDONE(status: error)
app-1  | 11 May 2024 19:26:59,290 [INFO] (rapid) INIT REPORT(durationMs: 28.548000)
app-1  | 11 May 2024 19:26:59,290 [INFO] (rapid) INVOKE START(requestId: 877a5e83-3bc1-4d4d-b99b-8ab054e77824)
app-1  | 11 May 2024 19:26:59,290 [ERROR] (rapid) Invoke failed error=Runtime exited with error: exit status 255 InvokeID=877a5e83-3bc1-4d4d-b99b-8ab054e77824
app-1  | 11 May 2024 19:26:59,290 [ERROR] (rapid) Invoke DONE failed: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,290 [WARNING] (rapid) Reset initiated: ReleaseFail
app-1  | 11 May 2024 19:26:59,290 [INFO] (rapid) Waiting for runtime domain processes termination
app-1  | 11 May 2024 19:26:59,454 [INFO] (rapid) INIT START(type: on-demand, phase: invoke)
app-1  | 11 May 2024 19:26:59,454 [INFO] (rapid) The extension's directory "/opt/extensions" does not exist, assuming no extensions to be loaded.
app-1  | 11 May 2024 19:26:59,454 [INFO] (rapid) Starting runtime without AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN , Expected?: false
app-1  | START RequestId: 1b75ed18-70d4-4454-b334-a52a59441d5c Version: $LATEST
app-1  | 11 May 2024 19:26:59,483 [WARNING] (rapid) First fatal error stored in appctx: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,483 [WARNING] (rapid) Process runtime-18 exited: exit status 255
app-1  | 11 May 2024 19:26:59,483 [INFO] (rapid) INIT RTDONE(status: error)
app-1  | 11 May 2024 19:26:59,483 [INFO] (rapid) INIT REPORT(durationMs: 29.313000)
app-1  | 11 May 2024 19:26:59,483 [INFO] (rapid) INVOKE START(requestId: 13ad4573-ba24-4f24-b294-f06babe32bf1)
app-1  | 11 May 2024 19:26:59,483 [ERROR] (rapid) Invoke failed error=Runtime exited with error: exit status 255 InvokeID=13ad4573-ba24-4f24-b294-f06babe32bf1
app-1  | 11 May 2024 19:26:59,483 [ERROR] (rapid) Invoke DONE failed: Runtime.ExitError
app-1  | 11 May 2024 19:26:59,483 [WARNING] (rapid) Reset initiated: ReleaseFail
app-1  | 11 May 2024 19:26:59,483 [INFO] (rapid) Waiting for runtime domain processes termination
app-1  | 502: UnknownError
app-1  |     at throwDefaultError (/local-api-gateway/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:8:22)
app-1  |     at /local-api-gateway/node_modules/@smithy/smithy-client/dist-cjs/default-error-handler.js:18:39
app-1  |     at de_InvokeCommandError (/local-api-gateway/node_modules/@aws-sdk/client-lambda/dist-cjs/protocols/Aws_restJson1.js:3346:20)
app-1  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)
app-1  |     at async /local-api-gateway/node_modules/@smithy/middleware-serde/dist-cjs/deserializerMiddleware.js:7:24
app-1  |     at async /local-api-gateway/node_modules/@aws-sdk/middleware-signing/dist-cjs/awsAuthMiddleware.js:14:20
app-1  |     at async /local-api-gateway/node_modules/@smithy/middleware-retry/dist-cjs/retryMiddleware.js:27:46
app-1  |     at async /local-api-gateway/node_modules/@aws-sdk/middleware-logger/dist-cjs/loggerMiddleware.js:7:26

Does anybody have any ideas as to how I go about debugging / fixing this?

Thanks in advance :)

Answered by mnapoli

May 14, 2024

Oh, there's no build process. You have to install Bref, that's part of the "Getting started" guides.

View full answer

mnapoli · 2024-05-12T15:36:02Z

mnapoli
May 12, 2024
Maintainer

I was able to reproduce with your example: HANDLER: public/index.php but the file is index.php. If I fix the file name I get everything working correctly. Does that help?

1 reply

mattspringbett May 12, 2024
Author

Thanks, I should have said that my index.php file is in the public folder as per the bref.sh example, I have updated my original post to show this.

mattspringbett · 2024-05-12T16:03:06Z

mattspringbett
May 12, 2024
Author

Another peculiar behaviour is that if I start the container, and then visit http://localhost:8000/index.php the browser save file dialog will open and if you proceed, will save the index.php file which is as per my code

3 replies

mnapoli May 13, 2024
Maintainer

Are you sure you don't have any other server running on that port?

mattspringbett May 13, 2024
Author

No other processes running on that port. I have also tried changing the port on the host to several other options (8002, 8321) etc and I get the same result each time

mnapoli May 14, 2024
Maintainer

I was going to ask to create a repository to reproduce it, but your descript kind of contains that already.

The only other explanation I could see is that you may have an old (broken?) version of the docker image, could you try pulling it (docker compose pull?) to ensure you have the latest version.

If that doesn't help, could you create a repository that reproduces it maybe? At least to be 100% sure we have the same setup.

mattspringbett · 2024-05-14T13:47:27Z

mattspringbett
May 14, 2024
Author

Ok, I have it working!

I had to start the container, then log onto the running container and run composer install manually.

Is this supposed to be the case, or should it run composer install as part of the container build process?

2 replies

mnapoli May 14, 2024
Maintainer

Oh, there's no build process. You have to install Bref, that's part of the "Getting started" guides.

Answer selected by mattspringbett

mattspringbett May 14, 2024
Author

Ah, my bad. Thanks for your help with us. Really appreciated.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

502 error developing with Docker locally #1806

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

502 error developing with Docker locally #1806

mattspringbett May 11, 2024

Replies: 3 comments · 6 replies

mnapoli May 12, 2024 Maintainer

mattspringbett May 12, 2024 Author

mattspringbett May 12, 2024 Author

mnapoli May 13, 2024 Maintainer

mattspringbett May 13, 2024 Author

mnapoli May 14, 2024 Maintainer

mattspringbett May 14, 2024 Author

mnapoli May 14, 2024 Maintainer

mattspringbett May 14, 2024 Author

mattspringbett
May 11, 2024

Replies: 3 comments 6 replies

mnapoli
May 12, 2024
Maintainer

mattspringbett May 12, 2024
Author

mattspringbett
May 12, 2024
Author

mnapoli May 13, 2024
Maintainer

mattspringbett May 13, 2024
Author

mnapoli May 14, 2024
Maintainer

mattspringbett
May 14, 2024
Author

mnapoli May 14, 2024
Maintainer

mattspringbett May 14, 2024
Author