You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've tried to deploy our APIP application based on the frankenPHP version 1.3.3 (with base image dunglas/frankenphp:1.3.3-builder-php8.2/dunglas/frankenphp:1.3.3-php8.2) in a AWS EKS cluster.
When the site is getting busy, the containers start to exit with code 139 very soon and we don't see any specific logs output.
However we still can't reproduce the same issue by load testing using tools like k6 in our testing environment.
Are you building with xcaddy? Which PHP extensions are you using? Are you using a PHP framework? Are you also seeing the same error when updating to frankenphp:1.3.6-php8.2 or if you disable opcache?
What happened?
We've tried to deploy our APIP application based on the frankenPHP version 1.3.3 (with base image dunglas/frankenphp:1.3.3-builder-php8.2/dunglas/frankenphp:1.3.3-php8.2) in a AWS EKS cluster.
When the site is getting busy, the containers start to exit with code 139 very soon and we don't see any specific logs output.
However we still can't reproduce the same issue by load testing using tools like k6 in our testing environment.
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Relevant log output
No response
The text was updated successfully, but these errors were encountered: